auth0-templates-scripts-utilsnpm
Malicious code in auth0-templates-scripts-utils (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package name impersonates the Auth0 ecosystem. Its postinstall hook (node index.js) runs unconditionally on npm install and performs a multi-stage data theft against the installer: (1) collects hostname, username, architecture, cwd, local IPs, /etc/resolv.conf,.git HEAD, UID/GID, the host project's package.json (name/version/repo) by walking parent directories, local and home .npmrc registry/scope settings, ~40 CI/CD environment variables (GITHUB_, GITLAB_, BITBUCKET_*, AWS CodeBuild, Vercel, etc.), and presence flags for ~/.ssh, ~/.aws, ~/.kube, ~/.docker, ~/.npm, ~/.gitconfig, ~/.cargo, ~/.ngrok; (2) when running in cloud, queries the instance metadata service at decimal-encoded 169.254.169.254 (2852039166) to extract live AWS IMDSv2 STS tokens, Azure IMDS OAuth tokens, and GCP service-account access tokens, including a 40-character prefix of each token in the payload; (3) DNS-probes ~30 internal-only hostnames (kubernetes.default.svc.cluster.local, vault.internal, consul.service.consul, gitlab.internal, jenkins.internal, ec2.internal, azure.internal, rancher.internal, etc.) to map the victim's internal infrastructure for lateral movement. The exfiltration destination dep-update-ci-02.lapxa354.workers.dev is base64-cloaked (Buffer.from("ZGVwLXVwZGF0ZS1jaS0wMi5sYXB4YTM1NC53b3JrZXJzLmRldg==","base64").toString()) and the data is sent in fragmented chunks via https.get with a 60-second delay as evasion. Code at index.js trims its own -utils suffix to derive an inferred host-project name and reports the host project rather than itself, confirming intent as a supply-chain delivery vehicle. User-Agent is MalekAbuLialaResearch/1.0.
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.
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 auth0-templates-scripts-utils (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auth0-templates-scripts-utils across your stack and pipelines.
If you installed it — respond
auth0-templates-scripts-utils 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 auth0-templates-scripts-utils 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 auth0-templates-scripts-utils 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 auth0-templates-scripts-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.