Which versions of @nasdtickets/common are malicious?

The following npm versions of @nasdtickets/common are flagged malicious: 1.0.23. Treat any of these as compromised.

How do I remediate @nasdtickets/common if I installed it?

@nasdtickets/common 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.

I already installed @nasdtickets/common — how do I know if it already compromised me?

If @nasdtickets/common was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @nasdtickets/common part of a known attack campaign?

Yes — @nasdtickets/common is associated with the IN-MAL-2026-014713 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @nasdtickets/common across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nasdtickets/common (version 1.0.23). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nasdtickets/common across your stack and pipelines.

Malicious package

@nasdtickets/commonnpm

@nasdtickets/common is a confirmed malicious npm package (MAL-2026-12324) that opens a backdoor for remote access (malicious version 1.0.23). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nasdtickets/common (npm)

MAL-2026-12324

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @nasdtickets/common

What this malware does

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.

Malicious versions

1 flagged

1.0.23

Indicators of compromise (SHA-256)

d260e32207d8cb161b0a72f1337a42c9755b9550a8eda1e70f0b4182273d476b

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nasdtickets/common (version 1.0.23). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nasdtickets/common across your stack and pipelines.
If you installed it — respond
@nasdtickets/common 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.
Did it already run?
If @nasdtickets/common was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @nasdtickets/common before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @nasdtickets/common on npm has been identified as a malicious package (version 1.0.23 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014713

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database