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

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

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

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

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

Yes — simple-date-formatter-util-4 is associated with the IN-MAL-2026-014431, IN-MAL-2026-014433 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-4 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-4 (2 malicious versions). 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-4 across your stack and pipelines.

Malicious package

simple-date-formatter-util-4npm

simple-date-formatter-util-4 is a confirmed malicious npm package (MAL-2026-12205) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simple-date-formatter-util-4 (npm)

MAL-2026-12205

Immediate action

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

npm uninstall simple-date-formatter-util-4

What this malware does

The package's npm postinstall script curls cloud instance-metadata endpoints (AWS 169.254.169.254, Alibaba 100.100.100.200, Tencent metadata.tencentyun.com and 169.254.0.23), retrieves the AWS IAM security-credentials for the attached instance role, lists /data/, and POSTs the collected output to a hardcoded attacker-controlled interact.sh (OAST) subdomain at ycrqyyjhwepdmhjifyccxss1hrks8lcd2.oast.fun. A bundled postinstall.js additionally reads the installer's ~/.ssh directory and POSTs username, platform, and key-file listings via HTTPS to the hardcoded IP 124.221.154.135:443/post. The declared package purpose (date formatting utility) has no relationship to cloud metadata queries or SSH-directory enumeration. Running npm install on this package hands short-lived IAM credentials and SSH material to the attacker.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

44b1bd8b606c30f6ac8c150379645ef93991c3864d4063891d5b2f96c1a4ff5d

f6ec6c790f702e0bb6617bb6bf16ad8b3a154bc7d539938535cde7a2cf205f17

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-4 (2 malicious versions). 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-4 across your stack and pipelines.
If you installed it — respond
simple-date-formatter-util-4 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-4 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-4 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-4 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014431IN-MAL-2026-014433

References

Credits

Amazon Inspector · finder

Detect & block this

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