Malicious code in @nasdtickets/common (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d260e32207d8cb161b0a72f1337a42c9755b9550a8eda1e70f0b4182273d476b) build/index.js (the package main) appends a hidden eval(atob('...')) block after the legitimate __exportStar boilerplate, separated by a long run of tab characters to push it off-screen in editors. On every require/import of the package, the decoded payload queries an Ethereum RPC/Blockscout endpoint for the latest transaction of the hardcoded EOA 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, interprets the 20-byte tx.to address as two encoded IPv4 addresses, and issues HTTP requests to http://<resolved-ip>:443/0x/cls and http://<resolved-ip>:443/0x/ls. The response carries a payload in the x-payload-b64 header that is XOR-decoded and then executed via spawn('node', ['-e', <decoded>], {detached: true, stdio: 'ignore', windowsHide: true}).unref(), launching a detached hidden Node process on the installer's machine. Module identifiers such as 'http', 'https', 'child_process', and 'spawn' are unicode-escaped (\u00XX) to further hide the behavior. The combination of on-chain C2 resolution (resistant to DNS/domain takedown), multi-layer obfuscation, and hidden detached process execution on import is a remote-code-execution supply-chain attack against any project that installs this version. ## Source: ghsa-malware (037f3ed4ca92b64733adaadc02c839d4fc180a4547c0a191cefb45a57e8833d5) 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.
AI Analysis
Technical Summary
The malicious code in @nasdtickets/common version 1.0.23 appends a hidden eval(atob('...')) block after legitimate exports, obfuscated with unicode escapes and whitespace to hide it from casual inspection. On import, it queries an Ethereum RPC endpoint for the latest transaction of a hardcoded externally owned account (EOA). It interprets the transaction's recipient address as two IPv4 addresses and sends HTTP requests to these resolved IPs to retrieve a base64-encoded payload from a custom header. This payload is XOR-decoded and executed by spawning a detached, hidden Node.js process on the victim's machine. This technique uses on-chain command and control (C2) resolution, making it resistant to traditional DNS or domain takedown, and constitutes a remote code execution supply-chain attack against any project that installs this specific package version.
Potential Impact
Any project or system that installs and imports @nasdtickets/common version 1.0.23 is at risk of remote code execution due to the hidden malicious payload execution. The attacker can execute arbitrary code on the victim's machine without user interaction beyond installing the package, potentially leading to full system compromise or further malicious activity. The use of blockchain-based C2 makes detection and mitigation more difficult.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package version. Users should immediately avoid installing or importing @nasdtickets/common version 1.0.23. Remove this package from all projects and replace it with a trusted alternative or a clean version if available. Monitor dependency sources carefully and verify package integrity before installation. Since this is a supply-chain attack, consider auditing all dependencies for similar malicious behavior.
Malicious code in @nasdtickets/common (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d260e32207d8cb161b0a72f1337a42c9755b9550a8eda1e70f0b4182273d476b) build/index.js (the package main) appends a hidden eval(atob('...')) block after the legitimate __exportStar boilerplate, separated by a long run of tab characters to push it off-screen in editors. On every require/import of the package, the decoded payload queries an Ethereum RPC/Blockscout endpoint for the latest transaction of the hardcoded EOA 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, interprets the 20-byte tx.to address as two encoded IPv4 addresses, and issues HTTP requests to http://<resolved-ip>:443/0x/cls and http://<resolved-ip>:443/0x/ls. The response carries a payload in the x-payload-b64 header that is XOR-decoded and then executed via spawn('node', ['-e', <decoded>], {detached: true, stdio: 'ignore', windowsHide: true}).unref(), launching a detached hidden Node process on the installer's machine. Module identifiers such as 'http', 'https', 'child_process', and 'spawn' are unicode-escaped (\u00XX) to further hide the behavior. The combination of on-chain C2 resolution (resistant to DNS/domain takedown), multi-layer obfuscation, and hidden detached process execution on import is a remote-code-execution supply-chain attack against any project that installs this version. ## Source: ghsa-malware (037f3ed4ca92b64733adaadc02c839d4fc180a4547c0a191cefb45a57e8833d5) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The malicious code in @nasdtickets/common version 1.0.23 appends a hidden eval(atob('...')) block after legitimate exports, obfuscated with unicode escapes and whitespace to hide it from casual inspection. On import, it queries an Ethereum RPC endpoint for the latest transaction of a hardcoded externally owned account (EOA). It interprets the transaction's recipient address as two IPv4 addresses and sends HTTP requests to these resolved IPs to retrieve a base64-encoded payload from a custom header. This payload is XOR-decoded and executed by spawning a detached, hidden Node.js process on the victim's machine. This technique uses on-chain command and control (C2) resolution, making it resistant to traditional DNS or domain takedown, and constitutes a remote code execution supply-chain attack against any project that installs this specific package version.
Potential Impact
Any project or system that installs and imports @nasdtickets/common version 1.0.23 is at risk of remote code execution due to the hidden malicious payload execution. The attacker can execute arbitrary code on the victim's machine without user interaction beyond installing the package, potentially leading to full system compromise or further malicious activity. The use of blockchain-based C2 makes detection and mitigation more difficult.
Mitigation Recommendations
No official patch or fix is currently available for this malicious package version. Users should immediately avoid installing or importing @nasdtickets/common version 1.0.23. Remove this package from all projects and replace it with a trusted alternative or a clean version if available. Monitor dependency sources carefully and verify package integrity before installation. Since this is a supply-chain attack, consider auditing all dependencies for similar malicious behavior.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12324
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735747bf8831d53915a097
Added to database: 08/05/2026, 15:31:19 UTC
Last enriched: 08/05/2026, 17:36:58 UTC
Last updated: 09/13/2026, 22:49:43 UTC
Views: 22
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.