Which versions of simple-date-formatter-util-16 are malicious?

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

How do I remediate simple-date-formatter-util-16 if I installed it?

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

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

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

Malicious package

simple-date-formatter-util-16npm

simple-date-formatter-util-16 is a confirmed malicious npm package (MAL-2026-12204) 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-util-16 (npm)

MAL-2026-12204

Immediate action

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

npm uninstall simple-date-formatter-util-16

What this malware does

package.json declares a postinstall script that runs automatically on npm install. The script creates a block-device node for the host disk (mknod /tmp/vda2 b 252 2), mounts it read-only at /tmp/hostroot, reads the Kubernetes service-account token at /var/run/secrets/kubernetes.io/serviceaccount/token, collects host and pod metadata (/etc/kubernetes, ARP table, internal work directories), and POSTs the aggregated output via curl to http://safjhdvsfwzhieemkdzbgr54r0yjhrmok.oast.fun/escinfo4. The behavior combines container-escape reconnaissance against a Kubernetes node with credential and host-data exfiltration to an out-of-band interaction domain.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3d57172cd3c0a47afc03e1a15ca2ead758bb6f5c78a2234d42487d65cb4944c5

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks simple-date-formatter-util-16-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