Which versions of datefmt-util-helper are malicious?

The following npm versions of datefmt-util-helper are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate datefmt-util-helper if I installed it?

datefmt-util-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 datefmt-util-helper — how do I know if it already compromised me?

If datefmt-util-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 datefmt-util-helper part of a known attack campaign?

Yes — datefmt-util-helper is associated with the IN-MAL-2026-017689, IN-MAL-2026-017690 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 datefmt-util-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 datefmt-util-helper (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datefmt-util-helper across your stack and pipelines.

Malicious package

datefmt-util-helpernpm

datefmt-util-helper is a confirmed malicious npm package (MAL-2026-13978) that opens a backdoor for remote access (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in datefmt-util-helper (npm)

MAL-2026-13978

Immediate action

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

npm uninstall datefmt-util-helper

What this malware does

Package presents itself as a date-formatting utility but ships a postinstall reverse shell. package.json declares scripts.postinstall = 'node postinstall.js'; postinstall.js hardcodes VPS = '8.135.48.40' and PORT = 4444 and runs execSync of a python3 -c payload that opens a socket to that host and invokes pty.spawn('/bin/bash'), with fallback branches using python3 subprocess and a Node net + child_process.spawn('/bin/bash') chain. Runs automatically during npm install, giving the remote host full interactive shell control on the installer's machine as the installing user. index.js implements a trivial date formatter as cover (a source comment translates to 'disguised as a normal date-formatting tool'); the library surface exists only to legitimize the package.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

54bb325784300096be6f67b12ea982f2f0ea239013b2ac86779b4fd485636da4

d897db063e1782ce6549adbac0736b75a2708f864c8eacfeaabac56b76c1bcbb

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 datefmt-util-helper (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datefmt-util-helper across your stack and pipelines.
If you installed it — respond
datefmt-util-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 datefmt-util-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 datefmt-util-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. datefmt-util-helper 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-017689IN-MAL-2026-017690

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks datefmt-util-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