Malicious code in @stellarshift/chain-metadata (npm)
Description
The npm package @stellarshift/chain-metadata versions 1.0.1 and 1.0.3 contain malicious code in their postinstall script that fetches and executes arbitrary code from a remote, unrelated Tencent Cloud URL. This execution occurs on macOS and Windows systems with specific software installed, targeting corporate developer workstations while evading CI and sandbox environments. The package falsely advertises no network calls and zero runtime dependencies, contradicting its actual behavior. Installation of this package can lead to full system compromise.
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 @stellarshift/chain-metadata npm package (versions 1.0.1 and 1.0.3) includes a postinstall lifecycle script that retrieves and executes code from an XOR-encoded URL decoded at runtime. The remote URL points to an anonymous Tencent Cloud COS bucket unrelated to the package publisher. On Unix systems, the payload is executed via a bash pipe; on Windows, via PowerShell with hidden process flags. Execution is restricted to environments where both Lark or Feishu clients and FortiClient VPN are installed, and it avoids running in CI environments by checking environment variables. This targeted execution aims to compromise corporate developer machines stealthily. The package's README misleadingly claims no network activity and zero runtime dependencies, which is false. The malicious code grants full control over the infected system.
Potential Impact
Any system with this package installed or running is considered fully compromised. Attackers may gain complete control over the machine, potentially accessing all stored secrets and keys. Because of the deep compromise, simply removing the package does not guarantee removal of all malicious artifacts. Immediate rotation of all secrets and keys from a separate, uncompromised system is necessary.
Mitigation Recommendations
No official patch or fix is currently documented. Users should immediately remove the affected package versions (1.0.1 and 1.0.3) from their systems. All secrets and keys stored on compromised machines must be rotated from a different, secure device. Due to the nature of the compromise, consider rebuilding or reimaging affected systems to ensure complete removal of malicious code. Monitor for any signs of persistence or further compromise.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-15822
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-vwjw-qgfw-xg9m"]
- Ecosystems
- ["npm"]
Threat ID: 6a998f5facd9273b49192d4f
Added to database: 09/03/2026, 15:16:47 UTC
Last enriched: 09/07/2026, 20:09:24 UTC
Last updated: 10/03/2026, 08:22:24 UTC
Views: 36
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.
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.