Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

simple-date-formatter-new-16npm

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

MAL-2026-17162
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall simple-date-formatter-new-16

What this malware does

package.json declares a postinstall lifecycle script that pipes a string-reversed shell one-liner through rev | bash, decoding to a bash reverse shell that opens /dev/tcp/124.221.154.135/4444 and attaches an interactive shell to it. This gives the publisher remote code execution on the installer's host at npm install time. The tarball also ships postinstall.js, which enumerates the installer's ~/.ssh directory, collects the filenames along with username and platform, and POSTs the JSON to https://124.221.154.135/post — direct exfiltration of SSH key material to the same hardcoded IP that receives the reverse shell. The obfuscation of the postinstall payload via string reversal and the mismatch between the package's advertised purpose (a date formatter) and its actual install-time behavior confirm malicious intent.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

5e57e9eff2fae987a2a23e3107d64c818e020b03380e31d6a3ae9cf8d4eb14ec

Detection & response playbook

Credential / info stealer
  1. 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-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-new-16 across your stack and pipelines.

  2. If you installed it — respond

    simple-date-formatter-new-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.

  3. Did it already run?

    If simple-date-formatter-new-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.

  4. How O3 protects you

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

simple-date-formatter-new-16 (npm) malicious package — MAL-2026-17162 | O3 Security