These seems completely reasonable. After posting 3 malicious packages they disabled all other packages for which he was a maintainer (could push updates).
"Accidentally" doesn't really fit with my reading. Maybe Stylus is clean but this move seems completely rational.
Fwiw, npm appears to be restoring access to the project https://github.com/stylus/stylus/issues/2938#issue-325479314...
Verifying that a package is unaffected can take some time. NPM may not know specifically when that package owner was compromised, or even if they've been a malicious actor the whole time, so the fact that there was no recent version isn't a guarantee of safety. Putting a security hold on the package in the meantime seems a reasonable approach.
> Stylus is relied upon by several popular frameworks including Angular 12. Admins should have at least checked this before pressing the kill switch.
That it's frequently downloaded also makes it more pressing to block if there's a reasonable chance that it contains malware.
I stopped using it because it has some issues with new CSS syntax, and the escape hatches for it are ugly and finicky
