Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

auth0-templates-scripts-utilsnpm

Malicious code in auth0-templates-scripts-utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4490
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall auth0-templates-scripts-utils

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

2 flagged
1.0.41.0.5

Indicators of compromise (SHA-256)

3ea3232ddda09bf884bbf590620c220141db593fe5b54073d0cd9e2d78a48e90
54baa6f0ec5a8bf259c5984579654ff2c4e2cc7cabab1b8e746c5e92d90072a2
b234a9ab8e82e317bb9b3c94fb6b6cad46167662e2d56a43a98083ca3d3ea43f
ed9a505fcbf6daef28b6625dcbde65ea1dd00b01c1a684debfdedfc7e5bc3643
5cd7e7327c9ded22d5a1c7cdd4d20a38c8465af033bb2438a59912beb1111974

Frequently asked questions

No. auth0-templates-scripts-utils on npm has been identified as a malicious package (versions 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003751IN-MAL-2026-003752IN-MAL-2026-003755IN-MAL-2026-003754GHSA-ff45-fchw-3969

References

Credits

  • Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
auth0-templates-scripts-utils (npm) malicious package — MAL-2026-4490 | O3 Security