mc-reg
This report shows the evidence for mc-reg@1.0.8. 7 of 8 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10637 confirms this npm version as malicious.
Advisory
MAL-2026-10637
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in mc-reg (npm)
Details
mc-reg advertises itself as a Cosmos chain-registry data package (README shows chain-registry-style `assets`/`chains`/`ibc` API), but its main and ESM entrypoints do not expose that data. Instead, index.js lazy-imports and re-exports `PartnerVaultHttpProvider` from an unrelated runtime dependency `chain-sdk-js`, and esm/index.js statically imports it — so `require('mc-reg')` or `import { chains } from 'mc-reg'` transparently pulls chain-sdk-js into the consumer's dependency tree. The pulled dependency's `persistence/chain.js` contains a wallet-secret interception + exfiltration pattern: a hardcoded destination reconstructed from a char-code array (`ping`/`ping`/`ping` decode-and-join sequence at lines 320-322 / 322-324) and POST calls (lines 118/204 and 120/206) that ship data to a non-caller-configured host, matching the shape of BIP-39 mnemonic / private-key theft from a wallet/signing path. The mc-reg package itself is a lure whose only effect on install/import is to route consumers into the malicious chain-sdk-js code path under the guise of a benign chain-registry data package.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The package contains a concrete install-time staged-payload launcher, but source facts do not establish that its malformed/ambiguous entrypoint executes successfully. Warn rather than block.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall, if the `apps` entry resolves and runs
Impact
Potential local code execution from a file outside the package boundary; execution is not confirmed due to the manifest/module mismatch.
Mechanism
external-file content piped into detached Node
AI rationale
The package contains a concrete install-time staged-payload launcher, but source facts do not establish that its malformed/ambiguous entrypoint executes successfully. Warn rather than block.
Evidence
package.jsonapps/index.js../../../public/logo.svg
Independent scan evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for AI warning decision
- Install hook invokes Node on `apps`.
- `apps/index.js` reads `../../../public/logo.svg`, outside the package root.
- It pipes that file's contents to a detached Node process and unreferences it.
Evidence against
- No network or credential-exfiltration code was found.
- The root manifest does not declare ESM mode although the lifecycle source uses ESM imports, so successful execution is not confirmed by source alone.
Behavioral surface
ChildProcessFilesystemShell
UrlStrings
NoLicense
Source & flagged code
3 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node apps
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg4"scripts": {
"build": "turbo build",
"dev": "turbo dev",
"lint": "turbo lint",
"format": "prettier --write \"**/*.{ts,tsx,md}\"",
"postinstall": "node apps"
},
High
•scripts.postinstall = node apps
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
2 High1 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSuspicious Lifecycle Evidencepackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to mc-reg@1.0.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing mc-reg@1.0.8. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.