Which versions of datetime-toolkit are malicious?

The following npm versions of datetime-toolkit are flagged malicious: 1.0.0, 1.0.4. Treat any of these as compromised.

How do I remediate datetime-toolkit if I installed it?

datetime-toolkit 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 datetime-toolkit — how do I know if it already compromised me?

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

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

Malicious package

datetime-toolkitnpm

datetime-toolkit is a confirmed malicious npm package (MAL-2026-5611) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in datetime-toolkit (npm)

MAL-2026-5611

Immediate action

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

npm uninstall datetime-toolkit

What this malware does

The package presents itself as a lightweight datetime utility but its main entry datetime.js invokes collect() from ./index.js at top level, so any require('datetime-toolkit') or import immediately triggers exfiltration. collect() serializes the entire process.env, the machine hostname, and a timestamp, AES-256-GCM-encrypts the JSON with a hardcoded key, and POSTs the result over plain HTTP to http://20.160.234.175:5000/collect. Strings and identifiers throughout index.js are obfuscated: the destination URL is built from \uXXXX escapes, the bearer token and encryption key are reverse-string literals ('nekot-terces' → secret-token, 'yek-noitpyrcne-tikloot-emitetad' → datetime-toolkit-encryption-key), and core APIs (http, crypto, os, process.env, POST, Authorization) are unicode-escaped. The package additionally ships a bin (cli.js) that runs the same collector behind a 'Collecting and sending…' spinner. The benign datetime/React helpers are a cover story; importing the package leaks CI secrets, cloud credentials, source tokens, and database passwords from any installer that loads it.

Malicious versions

2 flagged

1.0.01.0.4

Indicators of compromise (SHA-256)

0dc38777296d43cff21c9e56d16208c8925c6dc25b5dec4227823da94096433d

7724b8aace8cd3648792d8094d9434e47daff353c137b9df03849dd3a22b4943

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 datetime-toolkit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging datetime-toolkit across your stack and pipelines.
If you installed it — respond
datetime-toolkit 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 datetime-toolkit 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-toolkit 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-toolkit on npm has been identified as a malicious package (versions 1.0.0, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005700IN-MAL-2026-005861

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks datetime-toolkit-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