Which versions of date-fmt-utils-helper are malicious?

The following npm versions of date-fmt-utils-helper are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate date-fmt-utils-helper if I installed it?

date-fmt-utils-helper establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed date-fmt-utils-helper — how do I know if it already compromised me?

If date-fmt-utils-helper 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 date-fmt-utils-helper part of a known attack campaign?

Yes — date-fmt-utils-helper is associated with the IN-MAL-2026-017635 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 date-fmt-utils-helper 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 date-fmt-utils-helper (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 date-fmt-utils-helper across your stack and pipelines.

Malicious package

date-fmt-utils-helpernpm

date-fmt-utils-helper is a confirmed malicious npm package (MAL-2026-13947) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in date-fmt-utils-helper (npm)

MAL-2026-13947

Immediate action

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

npm uninstall date-fmt-utils-helper

What this malware does

The package presents itself as a date-formatting utility, but its index.js is a trivial cover and a source comment explicitly labels the library as a disguise. The package.json postinstall hook runs node postinstall.js on npm install, which opens a TCP connection to the hardcoded remote host 8.135.48.40:4444 and pipes /bin/sh stdio over the socket, with bash -i >& /dev/tcp/... and python3 pty.spawn fallbacks, giving the remote party interactive shell access on the installer's machine at install time. On failure the script beacons error details via HTTP GET to http://8.135.48.40/shell/failed and /shell/error, confirming the destination is attacker-controlled command-and-control infrastructure.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4ae88f68f30ebd69a595537393ce95c4ce5e543b558572769fa2c608fa1b1b0d

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for date-fmt-utils-helper (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 date-fmt-utils-helper across your stack and pipelines.
If you installed it — respond
date-fmt-utils-helper establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If date-fmt-utils-helper 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 date-fmt-utils-helper 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. date-fmt-utils-helper 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-017635

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks date-fmt-utils-helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database