Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

Malicious code in mci-sdk (npm)

0
Critical
Published: 06/16/2026 (06/16/2026, 22:17:46 UTC)
Source: GCVE Database
Product: mci-sdk

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1ae26c09350fdf9fb630e382c71dd730583ba1822122d232cde49a259597264f) On `npm install`, mci-sdk runs the postinstall hook `node./src/exec.js`, which imports `mci` from `src/core/index.js` and invokes it at module top level. The function reads a base64-encoded value stored as `MULTI_CHAIN_CONFIG.dev.apiKey` in `src/core/config.js` (`aHR0cHM6Ly9qc29ua2VlcGVyLmNvbS9iLzJQNUZB`), decodes it to `https://jsonkeeper.com/b/2P5FA`, fetches the JSON via axios, and pipes `response.data.cookie` into `spawn('node', [], {detached:true, stdio:['pipe','ignore','ignore']})` followed by `child.unref()`. The fetched payload is therefore executed as Node.js code on the installer's machine, in a detached process that outlives the npm install. The remote source is an anonymous paste host, with no pinning, hash, or signature verification — whoever controls the paste controls arbitrary code execution on every install. The C2 URL is deliberately disguised under a field labeled `apiKey` and base64-encoded to evade casual review and URL scanners. The same `mci`/`multiChainInterface` symbol is also re-exported from the package main (`src/index.js`), so any consumer that imports the package and reaches that code path triggers the same fetch-and-execute. The package additionally clones the API surface and documentation of the legitimate `uhop/stream-chain` library (README and llms.txt link to `github.com/uhop/stream-chain/wiki/...`) to attract developers seeking that package. ## Source: ghsa-malware (d0c6ac0d077500898b1b81d4fa254cb9242af2a7fdbf1d4eaf53666ecfe018b2) 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.

Affected software

npmghsa
mci-sdk
Affected versions
=1.2.8=1.2.10

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

AILast updated: 07/08/2026, 13:28:59 UTC

Technical Analysis

The mci-sdk npm package (versions 1.2.8 and 1.2.10) includes a postinstall script that decodes a base64-encoded URL pointing to an anonymous paste host. It fetches JSON data containing a 'cookie' field, which is then executed as Node.js code in a detached child process. This allows arbitrary code execution on the installer's machine, with the malicious payload controlled remotely and without any integrity verification. The package also exports this malicious functionality at runtime, triggering the same remote code execution when imported. The package mimics the API and documentation of the legitimate 'uhop/stream-chain' library to lure developers. Due to the nature of this backdoor, any system with this package installed is considered fully compromised.

Potential Impact

Systems with mci-sdk versions 1.2.8 or 1.2.10 installed are subject to remote arbitrary code execution controlled by an attacker via a malicious payload fetched during installation and runtime. This can lead to full system compromise, including unauthorized access to secrets and keys stored on the machine. The malicious process runs detached and persists beyond the npm install lifecycle, making removal difficult and increasing the risk of persistent backdoors.

Mitigation Recommendations

No official patch or fix is available for this malicious package. Immediate removal of the mci-sdk package versions 1.2.8 and 1.2.10 is strongly recommended. Because the package executes remote code and may have fully compromised the system, all secrets and keys stored on the affected machine should be rotated from a separate, trusted device. Consider rebuilding or thoroughly cleaning the affected system to ensure removal of any persistent malicious components. Exercise caution when installing packages from untrusted sources and verify package authenticity before use.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
MAL-2026-5931
Osv Schema Version
1.7.4
Aliases
["GHSA-7cjh-m5vf-hp3r"]
Ecosystems
["npm"]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a4e4ed0c9d9e3dbe3287b9d

Added to database: 07/08/2026, 13:21:20 UTC

Last enriched: 07/08/2026, 13:28:59 UTC

Last updated: 07/29/2026, 12:14:12 UTC

Views: 21

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses