Which versions of simple-date-formatter-new-4 are malicious?

The following npm versions of simple-date-formatter-new-4 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate simple-date-formatter-new-4 if I installed it?

simple-date-formatter-new-4 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.

I already installed simple-date-formatter-new-4 — how do I know if it already compromised me?

If simple-date-formatter-new-4 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.

Is simple-date-formatter-new-4 part of a known attack campaign?

Yes — simple-date-formatter-new-4 is associated with the IN-MAL-2026-014420 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find simple-date-formatter-new-4 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for simple-date-formatter-new-4 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging simple-date-formatter-new-4 across your stack and pipelines.

Malicious package

simple-date-formatter-new-4npm

simple-date-formatter-new-4 is a confirmed malicious npm package (MAL-2026-12196) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simple-date-formatter-new-4 (npm)

MAL-2026-12196

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall simple-date-formatter-new-4

What this malware does

Package advertises itself as a date-formatting utility but its actual behavior on install is credential theft and internal-network reconnaissance. The postinstall script in package.json runs a shell one-liner that probes internal Kubernetes API endpoints, dumps /etc/resolv.conf and ip route, TCP-scans internal hosts, reads the pod's Kubernetes service-account token from /var/run/secrets/kubernetes.io/serviceaccount/token, and POSTs the aggregated output via curl to a hardcoded OAST (interact.sh) collector at http://safjhdvsfwzhieemkdzbgr54r0yjhrmok.oast.fun/escinfo8. A bundled postinstall.js additionally enumerates ~/.ssh (listing public keys), collects the local username and platform, and POSTs the JSON to a hardcoded IP 124.221.154.135 over HTTPS; in-file comments describe it as an SSH-key theft C2 demo. The library payload (index.js) is a three-line wrapper around toLocaleDateString, functioning solely as cover for the install-time attack.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2f5ed3c402677fcfaeac396b55b9db5280445e9b0130133cc311a83f96f2a0de

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for simple-date-formatter-new-4 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging simple-date-formatter-new-4 across your stack and pipelines.
If you installed it — respond
simple-date-formatter-new-4 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 simple-date-formatter-new-4 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 simple-date-formatter-new-4 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

No. simple-date-formatter-new-4 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014420

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database