Which versions of mc-provider are malicious?

The following npm versions of mc-provider are flagged malicious: 1.0.10. Treat any of these as compromised.

How do I remediate mc-provider if I installed it?

mc-provider 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 mc-provider — how do I know if it already compromised me?

If mc-provider 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 mc-provider part of a known attack campaign?

Yes — mc-provider is associated with the IN-MAL-2026-018427 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 mc-provider 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 mc-provider (version 1.0.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mc-provider across your stack and pipelines.

Malicious package

mc-providernpm

mc-provider is a confirmed malicious npm package (MAL-2026-14305) that steals credentials and exfiltrates sensitive data (malicious version 1.0.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mc-provider (npm)

MAL-2026-14305

Immediate action

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

npm uninstall mc-provider

What this malware does

Package metadata describes mc-provider as 'Theta chain registry ⚛️' and the README is a verbatim copy of the hyperweb-io/chain-registry README instructing consumers to import { assets, chains, ibc } from 'mc-provider'. The actual main entry does not export any of those symbols. Instead, index.js dynamically loads an unrelated runtime dependency named supersig (providerPromise = import('supersig').then((mod) => mod.HttpProvider)) and re-exports supersig's HttpProvider under this package's name; esm/index.mjs does the same via import { HttpProvider } from 'supersig'; export { HttpProvider };. Bundled chains/assets/IBC JSON files are present as decoys but are not reachable through the package's exports. Consumers following the README end up with a supersig-backed HTTP/RPC provider handling their Cosmos JSON-RPC and signing traffic — code they never chose to install, sourced from a package whose contents are outside this record. The impersonation of a well-known Cosmos registry package combined with silent resolution to an unrelated third-party provider is the standard shape used to insert attacker-controlled RPC/signing code into a wallet or dApp dependency tree.

Malicious versions

1 flagged

1.0.10

Indicators of compromise (SHA-256)

e494af2871662b1b342a26141de010623484dfef353b505805f4b41d85d775c1

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 mc-provider (version 1.0.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mc-provider across your stack and pipelines.
If you installed it — respond
mc-provider 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 mc-provider 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 mc-provider 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. mc-provider on npm has been identified as a malicious package (version 1.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018427

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mc-provider-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