Which versions of datetime-toolkit are malicious?

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

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

Remove datetime-toolkit 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is datetime-toolkit part of a known attack campaign?

Yes — datetime-toolkit is associated with the IN-MAL-2026-005700 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect datetime-toolkit in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking datetime-toolkit and packages like it before any post-install script runs.

Malicious package

datetime-toolkitnpm

Malicious code in datetime-toolkit (npm) Remove it immediately and rotate any exposed credentials.

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

1 flagged

1.0.4

Indicators of compromise (SHA-256)

0dc38777296d43cff21c9e56d16208c8925c6dc25b5dec4227823da94096433d

Frequently asked questions

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

Campaign

IN-MAL-2026-005700

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection