Skip to main content
MalwarePublished

@nasddatax/common (npm) · Malicious Code

Affects @nasddatax/commonSource GCVE Database

0

Malicious package : remove @nasddatax/common and rotate any secrets on hosts that installed it.

Data as of 6 Aug 2026, 18:24 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-12323

What to do

Remove @nasddatax/common from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
npm@nasddatax/commonAffected
  • =1.0.21
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1cf5662d7c8759acd7a9a541baddd3bf4787594fafcd38f8a4eaf27bbe57d558) build/index.js appends an eval(atob(...)) trailer after legitimate re-exports. On require, the decoded loader queries public Ethereum JSON-RPC endpoints for the latest transaction from the hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes the 20-byte tx.to value into two IPv4 addresses, fetches an XOR-obfuscated JavaScript payload from http://<ip>:443/0x/cls and http://<ip>:443/0x/ls, decodes an x-payload-b64 response header, and executes the result via eval and a detached spawn('node', ['-e', payload]). Security-relevant identifiers (http, child_process, spawn, method and header strings) are written as \u00XX unicode escapes to hide the behavior. Any application that requires this package runs attacker-controlled code on the installer's machine, and the C2 destination can be rotated on-chain without republishing the package. Package metadata (empty author, empty description, scoped `<scope>/common` name) is consistent with an impostor common-utilities package. ## Source: ghsa-malware (db85c2c336b7b7965deef4783c3eddd656dbaf384c2c73b5d50167ef308fa5e9) 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.

References

Community reviews

Loading reviews…