abuden227

The tarball ships `auto-publish.sh`, a script that republishes the same payload under ~100 distinct npm names (`ishowfeet1`-`ishowfeet20`, `nottuff1`-`nottuff30`, `abuden*`, `imillegal*`, `ratelimitsucks*`, etc/) by rewriting `package.json.name` and running `npm publish --silent` in a loop — namespace-spam infrastructure shipped inside the package itself. The package's declared `main` is `sw.js`, a browser Service Worker (`importScripts('./8cfc2/hgshm.js')`, `self.addEventListener('install'|'activate'|'fetch'|'message')`) that throws immediately if loaded from Node. The shipped assets are a heavily obfuscated Ultraviolet/bare-mux web-proxy frontend with an `index.html` themed as "Riverbend Tutoring" that hides a popunder redirect to `https://abdct.com/` on click/keydown/touchstart. `package.json` declares no `preinstall`/`install`/`postinstall`/`prepare` hooks, and `require('ishowfeet9')` from Node fails before any code runs, so a Node installer experiences no auto-execution. The harm is registry abuse (mass-publication of a misleading name family) and a browser-side proxy/popunder served to whoever later loads these static assets — not installer-side compromise. Routing to human review for namespace-abuse adjudication. ## Source: ghsa-malware (5c7a1e4bfa19fe7b69a7d32595b651adc58bfd71c9cd8362fcff3606bdc0a531) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.