datetime-toolkit@1.0.1

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. ## Source: ghsa-malware (7d997e277a4f73cc68d97e58d8296a07af2ff574861d1277634d628b27187488) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.