NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dateuuidv2npm

Advisory published Updated

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

Malicious code in dateuuidv2 (npm)

MAL-2026-12176
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dateuuidv2

What this malware does

The package advertises itself as a UUID v7 generator, but its main entry loads lib/bootstrap.js which unconditionally invokes extractDateISO() at require time. That function reads a PORT= value from README.md in the current working directory, uses those digits to reconstruct an AES-256-GCM key/IV, and decrypts a hardcoded ciphertext to recover a C2 URL. It then POSTs the installer's OS platform and release string to that URL, and executes the response body: on Windows it writes the response to %TEMP%/temp_<timestamp>.vbs (extension built as '.v'+'b'+'s' to avoid a literal.vbs string) and runs it via child_process.exec, then unlinks the file. Multiple evasion layers are present: AES-GCM ciphertext for the destination URL, key material sourced from a file the operator is told to seed with a PORT= value, and string-concatenated dropper extension. The advertised UUID functionality is unrelated to any of the network I/O or shell execution behavior.

Malicious versions

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

4165eefd9d54cf18f222a72424f4c4c5fbce30c6f81d4dfdbea6fac7a050e6ed
fe45b7e605cc8d939075909d39c9b8a392428c4cc1068f23cd201e2ba3817d1b
a15649ce278832166c0fc4b80206329a54347bf748b207c088308e72a31f72f1

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for dateuuidv2 (3 malicious versions).

  2. If you installed it — respond

    dateuuidv2 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.

  3. Did it already run?

    If dateuuidv2 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. dateuuidv2 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014622IN-MAL-2026-014620IN-MAL-2026-014815

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dateuuidv2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

dateuuidv2 (npm) malicious package — MAL-2026-12176 | O3 Security