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

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

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

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

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

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

Malicious package

simple-date-formatter-new-1npm

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

MAL-2026-11502

Immediate action

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

npm uninstall simple-date-formatter-new-1

What this malware does

On npm install, the package.json postinstall hook executes a shell one-liner that attempts to mount the host block device via mknod, enumerates /etc/kubernetes and kubelet pod directories, reads the Kubernetes service-account token at /var/run/secrets/kubernetes.io/serviceaccount/token, lists home directory contents, and POSTs the collected output to http://safjhdvsfwzhieemkdzbgr54r0yjhrmok.oast.fun/escinfo4 (an interact.sh OAST callback subdomain). A sibling postinstall.js in the tarball reads the installer's ~/.ssh directory via getSSHKeys() and POSTs a JSON payload containing SSH contents, username, and platform to hardcoded IP 124.221.154.135 on port 443. The package advertises itself as a date formatter but ships no such functionality; its only effect on install is host reconnaissance and credential exfiltration.

The OpenSSF Package Analysis project identified 'simple-date-formatter-new-1' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

037638085662ef2cec04655349a528b60480aa642606d96eba158e62161b3a51

628527c388185356d23a8905edf240a32c062afb06c00a58c0101ffd4bcc5182

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

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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