Why is an obfuscated JavaScript payload part of an NPM command?
github.com
github.com
This should've been a pretty clear hint that this sort of thing is not ok.
I develop in this ecosystem regularly and I'm still waiting for the day that everyone else acknowledges that downloading and running arbitrary code is a bug, not a feature...
I think I'll be waiting forever - this sets a really bad example.
> Hi, While I appreciate easter eggs (and think others have it a bit too much out for them), the fact that this easter egg is obfuscated sets off multiple alarm bells. The automated code scanners were right -- this looks like malware!
> [...]
> If this easter egg was unobfuscated, I would've just looked at it and gone "thats neat", but the fact that this was obfuscated to look like malware means I have to spend 10 mins checking that it isn't actually malicious. It would be nice if the easter egg was kept but de-obfuscated so others aren't concerned by it.