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

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

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

simple-date-formatter-new-14 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-14 — how do I know if it already compromised me?

If simple-date-formatter-new-14 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-14 part of a known attack campaign?

Yes — simple-date-formatter-new-14 is associated with the IN-MAL-2026-020510 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-14 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-14 (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-14 across your stack and pipelines.

Malicious package

simple-date-formatter-new-14npm

simple-date-formatter-new-14 is a confirmed malicious npm package (MAL-2026-17160) 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-14 (npm)

MAL-2026-17160

Immediate action

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

npm uninstall simple-date-formatter-new-14

What this malware does

The package presents itself as a date-formatting utility (index.js is a 160-byte formatDate stub) but the published tarball contains an SSH-key exfiltration payload and an install-time DNS beacon. package.json declares a postinstall lifecycle script that runs 'nslookup 9e954818.log.dnslogs.dpdns.org', causing every installer to beacon a per-package token to attacker-controlled DNS logging infrastructure at install time, leaking installer presence and resolver IP. A sibling postinstall.js reads ~/.ssh (enumerating.pub files and related host/user identifiers) and POSTs the collected data over HTTPS to a hardcoded bare IP endpoint at https://124.221.154.135/post; comments in the file describe SSH key theft and C2 exfiltration. The name-collision between the declared postinstall hook and the stealer filename, combined with the empty author field and typosquat-style package name, is consistent with a disposable supply-chain payload.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cbe2adf4e9d3b54b33c0e80285a5b0eb4d81dfde75c7a5b7a202ac43793268cd

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-14 (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-14 across your stack and pipelines.
If you installed it — respond
simple-date-formatter-new-14 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-14 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-14 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-14 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-020510

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks simple-date-formatter-new-14-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