The fake browser update scam gets a makeover
So the attack goes: 1) compromise some site to serve arbitrary JS 2) have it serve simple JS that requests <i>other</i> JS that contains the real malicious payload.<p>And the reason for this two-step architecture is to make it convenient to change the real payload.<p>And the problem is where to host the real payload. The first idea was Cloudflare, but Cloudflare keeps taking that sort of thing down. So now they host it "on the blockchain" which means it "can’t be blocked".<p>What I don't understand is who is actually serving the HTTP call that effectively proxies the data from the blockchain. It seems like they (like Cloudflare, or a regular hosting service) are opening themselves up to all sorts of risks by serving arbitrary content.