Which versions of date-utils-light are malicious?

The following npm versions of date-utils-light are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate date-utils-light if I installed it?

date-utils-light 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-utils-light — how do I know if it already compromised me?

If date-utils-light was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is date-utils-light part of a known attack campaign?

Yes — date-utils-light is associated with the IN-MAL-2026-010721 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-utils-light across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for date-utils-light (version 1.0.1).

Malicious package

date-utils-lightnpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

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

Malicious code in date-utils-light (npm)

MAL-2026-10731

Immediate action

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

npm uninstall date-utils-light

What this malware does

Package presents itself as a trivial date-formatting utility (index.js exports a one-line ISO date helper) but ships a postinstall.js that runs automatically on npm install. The script shells out via child_process.exec to collect host reconnaissance — hostname, whoami, id, uname, pwd, /etc/os-release, HOME, SHELL, container indicators, /proc/1/cgroup, network interfaces, and running process list — base64-encodes the data, and sends it via HTTP GET to a hardcoded Burp Collaborator subdomain at pwpzhsrbtvmfqrqr7onqcwnrcii960up.oastify.com/ing?d=<base64>. The stated purpose of the package does not require any shell execution or network activity; the install-time reconnaissance beacon is unrelated to the advertised functionality.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

99bd644fd9a59518d6f77e8d76c077ffef8a2afdc7ae2b00a6ca87299879a671

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for date-utils-light (version 1.0.1).
If you installed it — respond
date-utils-light 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-utils-light was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. date-utils-light on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010721

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks date-utils-light-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