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

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

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

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

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

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

Malicious package

simple-date-formatter-new-3npm

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

MAL-2026-12195

Immediate action

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

npm uninstall simple-date-formatter-new-3

What this malware does

The package's postinstall script in package.json runs a shell pipeline that collects host and container-runtime information (kernel version via uname -r, /proc/1/cmdline, /proc/1/ns, root filesystem listing, block device listing) and POSTs the output via curl to the hardcoded interact.sh-style callback http://safjhdvsfwzhieemkdzbgr54r0yjhrmok.oast.fun/escinfo7. The same pipeline attempts container-escape actions: creating a cgroup subtree under /sys/fs/cgroup/esc7, moving PID 0 into it, mknoding a block device at /tmp/x17, and mounting the host root filesystem at /tmp/hostroot, with results reported back to the same external endpoint. The tarball also ships a postinstall.js that enumerates the installer's ~/.ssh directory and POSTs the listing plus username/platform to the hardcoded IP 124.221.154.135:443/post, with in-source comments describing the behavior as SSH-key C2 exfiltration. All of this runs automatically on npm install with no user consent. The package name and stated purpose ("date formatter") do not match any of the observed behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

eaef04a98dce874de04a92b580f4f919067a0e492d38dff69a57fc09db1cfe14

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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