Which versions of mdb-vite are malicious?

The following npm versions of mdb-vite are flagged malicious: 1.5.2. Treat any of these as compromised.

How do I remediate mdb-vite if I installed it?

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

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

Yes — mdb-vite is associated with the GHSA-w572-cxjv-46jc, IN-MAL-2026-009793 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 mdb-vite 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 mdb-vite (version 1.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mdb-vite across your stack and pipelines.

Malicious package

mdb-vitenpm

mdb-vite is a confirmed malicious npm package (MAL-2026-10144) that steals credentials and exfiltrates sensitive data (malicious version 1.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mdb-vite (npm)

MAL-2026-10144

Immediate action

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

npm uninstall mdb-vite

What this malware does

The package's default export getPlugin performs an HTTPS fetch to https://svganchordev.net/icons/107 with URL components split across protocol, domain, separator, and path variables to disguise the destination, then passes the response's credits field to new Function('require','module',...,data.credits) and invokes it with full Node capabilities (require, module, process, Buffer, global, __dirname=process.cwd()). Any consumer that imports the package and invokes the default export runs attacker-controlled code with the installer's Node privileges — enabling arbitrary payload delivery, credential theft, persistence, or downstream compromise. Additional misdirection: the package name mdb-vite evokes MDBootstrap/Vite tooling, keywords are react, helper, svg, the README titles itself polymarket-clob-api, and package.json describes it as a Polymarket CLOB SDK — none of which match the code, which only fetches and evals remote JavaScript. A bearrtoken: 'logo' header and an unused CDN-provider map (cloudflare/fastly/akamai/cloudfront) are decoys to make the loader appear CDN-related.

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.

Malicious versions

1 flagged

1.5.2

Indicators of compromise (SHA-256)

5e2c6b3eff8c409ee862db83e5d1211582cd14238384a89c0bc6b31b16fbead7

d24ffe7ac6e64aab50d9ba84f5b06ffd1047663698d25071770749b36afe6543

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

Campaign

GHSA-w572-cxjv-46jcIN-MAL-2026-009793

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mdb-vite-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