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

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

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

Remove simple-date-formatter-new-8 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

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

Malicious package

simple-date-formatter-new-8npm

simple-date-formatter-new-8 is a confirmed malicious npm package (MAL-2026-12199) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12199

Immediate action

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

npm uninstall simple-date-formatter-new-8

What this malware does

The package.json postinstall script runs unconditionally on npm install, collecting host and internal-network reconnaissance (kernel version via uname -r, /etc/resolv.conf, hostname -I, /proc/net/route, internal TCP endpoint probes, and Kubernetes API probes against 10.45.196.x /version and /api/v1/namespaces) and POSTs the aggregated output via curl to an attacker-controlled interact.sh OAST collector at http://safjhdvsfwzhieemkdzbgr54r0yjhrmok.oast.fun/escinfoF. A sibling postinstall.js enumerates the installer's ~/.ssh directory and POSTs the contents along with username and platform to a hardcoded remote host at 124.221.154.135:443/post. The declared purpose is a trivial date formatter, which has no legitimate need to read SSH material, enumerate internal networks, or contact OAST infrastructure.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4f0bf9e4040cf2940b0ca9a9e5cea7def2c660925afd0ba959ed69d28ca007b7

Detection & response playbook

Malicious package

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-8 (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-8 across your stack and pipelines.
If you installed it — respond
Remove simple-date-formatter-new-8 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If simple-date-formatter-new-8 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-8 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-8 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-014422

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database