VDB
Sign up

MAL-2026-15560

Malicious code in supersignaturenature (npm)

Details

--- _-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (ab1df02839294b29ff278b7a80505be50de75eb0f317f4bf29635236a75e4b15) The published dist/ bundles (main/module/browser entrypoints) contain code absent from the src/ tree: at library load they read an encrypted rsaToken from a package file via readRSAFromPackage(), DES-decrypt it using a key imported from the dependency manager-thedate, and pipe the plaintext into child_process.spawn('node', [],...) via stdin, executing the decrypted JavaScript in the installer's Node process. The DES key dependency is declared as "manager-thedate": "latest" in package.json, so the effective payload can be changed at any time by whoever controls that dependency, even though supersignaturenature itself is version-pinned. The src/ tree implements a straightforward Theta blockchain client with no fs, child_process, DES, or spawn usage; the shipped dist/*.js contains var child_process = require('child_process'), function decryptToken(token, password) using CryptoJS.DES.decrypt, readRSAFromPackage, and rsa_exec.stdin.write(String(rsaDecrypted)) against a spawned node process. The runtime code is not a rollup of the shipped source, so review of src/ does not reveal the loader that consumers actually execute.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm/supersignaturenature

No fixed version published yet for supersignaturenature (npm). Pin to a known-safe version or switch to an alternative.

References