notafollower122npm
notafollower122 is a confirmed malicious npm package (MAL-2026-14035) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in notafollower122 (npm)
What this malware does
package.json declares a postinstall lifecycle script that runs automatically on npm install. The script uses child_process to query the AWS ECS container metadata endpoint (ECS_CONTAINER_METADATA_URI_V4/task), which returns the cluster name, AWS account ID, task ARN, and container image list for the installer's ECS task, then POSTs the response body to the hardcoded ngrok tunnel https://mourner-slot-explicit.ngrok-free.dev via curl -X POST... --data-binary @-. The package ships only package.json with no source, build artifacts, or documented functionality, so the postinstall has no legitimate purpose. The destination is an anonymous, mutable ngrok tunnel with no relationship to any publisher — the shape of cloud-environment reconnaissance and exfiltration against AWS ECS installers.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for notafollower122 (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging notafollower122 across your stack and pipelines.
If you installed it — respond
notafollower122 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If notafollower122 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks notafollower122 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks notafollower122-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.