NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

zer0onedatenpm

Advisory published Updated

zer0onedate is a confirmed malicious npm package (MAL-2026-5535) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zer0onedate (npm)

MAL-2026-5535
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall zer0onedate

What this malware does

On npm install, postinstall.js executes a chain of curl commands that read cloud instance metadata service (IMDS) endpoints — AWS (169.254.169.254/latest/meta-data/iam/security-credentials/), Alibaba/Aliyun and Tencent metadata hosts, plus 100.100.100.200 and 169.254.0.23 — and writes the responses to /tmp/aws.txt, /tmp/ali.txt, /tmp/meituan.txt. It also probes an internal-looking SSRF endpoint at https://mtsrc-test.sankuai.com/ssrf and lists /data/. The aggregated contents are POSTed via curl -X POST -d to http://h4mx6b7krgzarfehbutwabxbu20tojc8.oastify.com/metadata, an attacker-controlled Burp Collaborator subdomain. Any installer running in AWS/Aliyun/Tencent cloud (CI runners, build agents, cloud dev VMs) leaks temporary IAM credentials from IMDS to the attacker, who can then pivot into the victim's cloud account. The targeting of Meituan-internal infrastructure (sankuai.com) plus multiple non-standard cloud metadata IPs indicates deliberate reconnaissance, not opportunistic theft.

Malicious versions

2 flagged
1.0.01.0.2

Indicators of compromise (SHA-256)

106494bfe4420962c30d8b3989a1397d197f277079c71b8d15695c9128d72399
d6d3b1cca8ae0369474912f980f89947449995895ed0238ac2444063dbd957e1

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for zer0onedate (2 malicious versions).

  2. If you installed it — respond

    zer0onedate 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.

  3. Did it already run?

    If zer0onedate was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. zer0onedate on npm has been identified as a malicious package (versions 1.0.0, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005329IN-MAL-2026-005328

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks zer0onedate-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

zer0onedate (npm) malicious package — MAL-2026-5535 | O3 Security