The 'ishowfeet1' npm package includes a script 'auto-publish.sh' that republishes the same payload under approximately 100 distinct npm package names by modifying 'package.json.name' and running 'npm publish' in a loop, creating namespace-spam infrastructure. The declared main file is a browser Service Worker ('sw.js') that loads an obfuscated web proxy frontend themed as 'Riverbend Tutoring' and triggers a popunder redirect to 'https://abdct.com/' upon user interaction. The package does not execute code during Node.js installation, and requiring the package in Node fails before execution, indicating no installer-side compromise. The primary harm is abuse of the npm registry namespace and malicious browser-side proxy and redirect behavior when the static assets are loaded. The package is under human review for namespace abuse adjudication. A separate source claims that any computer with this package installed or running should be considered fully compromised, recommending immediate secret/key rotation and package removal, though removal may not eliminate all malicious software.

The impact includes abuse of the npm registry namespace through mass publication of misleading package names, potentially deceiving users. When the package's browser Service Worker assets are loaded, users are exposed to a heavily obfuscated web proxy frontend and a hidden popunder redirect to a malicious website, which could lead to further compromise or unwanted behavior. There is no direct installer-side compromise or automatic code execution during Node.js installation, but the presence of the package on a system is considered a critical security risk, with recommendations to treat affected systems as fully compromised and rotate all secrets and keys.

No official patch or fix is indicated. The package should be removed immediately from any system where it is installed or running. All secrets and keys stored on affected computers should be rotated from a separate, trusted device. Because the package does not auto-execute code during installation, the main risk is from loading its browser assets; avoid loading or running these assets in browsers. The package is under human review for namespace abuse, so monitor the npm registry for updates on its status. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance.