Malicious code in notafollower122 (npm)
The npm package notafollower122 contains malicious code in a postinstall lifecycle script that exfiltrates AWS ECS container metadata (cluster name, account ID, task ARN, container images) to an anonymous ngrok tunnel.
- Disclosed
- Last updated
- Blast radius
- AWS ECS environments running npm install on notafollower122
- Ecosystems
- Attack vectors
- Affected entities
- notafollower122npm package containing malicious postinstall script
The npm package notafollower122 was published with a malicious postinstall lifecycle script that executes automatically during npm install. The script uses Node.js child_process to query the AWS ECS container metadata endpoint (ECS_CONTAINER_METADATA_URI_V4/task), retrieving sensitive environment information including cluster name, AWS account ID, task ARN, and container image list.\n\nThe exfiltrated data is sent via HTTP POST to a hardcoded ngrok tunnel endpoint (https://mourner-slot-explicit.ngrok-free.dev) using curl. The package contains only a package.json file with no legitimate source code, build artifacts, or documented functionality, indicating the postinstall script serves no legitimate purpose.\n\nThe destination is an anonymous, mutable ngrok tunnel with no relationship to the package publisher, consistent with cloud-environment reconnaissance and credential/metadata exfiltration targeting AWS ECS deployments. This attack is particularly dangerous in containerized CI/CD and deployment environments where AWS credentials and sensitive metadata are accessible.\n\nThe incident was identified and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- notafollower122
- Domains
- mourner-slot-explicit.ngrok-free.dev
Remediation
- Immediately remove notafollower122 from all npm dependencies and lock files
- Audit npm install logs and CI/CD pipeline execution logs for any installations of notafollower122
- If notafollower122 was installed in an AWS ECS environment, assume AWS credentials and container metadata may be compromised; rotate all AWS IAM credentials and review CloudTrail logs for unauthorized activity
- Review ngrok tunnel logs if accessible to determine what data was exfiltrated
- Implement npm package scanning and allowlisting in CI/CD pipelines to prevent installation of unknown or suspicious packages
- Use npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-9gjh-495m-x59v · GitHub Advisory Database
Cite this entry
"Malicious code in notafollower122 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 14, 2026; last updated August 14, 2026. https://supplychainattack.org/incident/malicious-code-in-notafollower122-npm-ubka6o
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package