Which versions of vite-plugin-model are malicious?

The following npm versions of vite-plugin-model are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate vite-plugin-model if I installed it?

Remove vite-plugin-model from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed vite-plugin-model — how do I know if it already compromised me?

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

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

Malicious package

vite-plugin-modelnpm

Malicious code in vite-plugin-model (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10545

Immediate action

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

npm uninstall vite-plugin-model

What this malware does

The CJS entrypoint dist/index.js top-level requires bytenode and loads a sibling V8 bytecode blob dist/index.jsc, then injects a hidden Model.resetor() that instantiates a class from that bytecode and immediately calls its queryDBConnect() method on require(). The bytecode contains axios, atob, and node:module internals (_compile, _nodeModulePaths), together with a reversed-base64 literal that decodes to https://c0uxnElubanuzwji03vsfrj.m.pipedream.net — an HTTPS Pipedream webhook. The runtime pattern fetches the webhook response, decodes it, and compiles it as a new Node module, executing attacker-controlled code on the installer's machine as soon as any consumer imports the package. Additional indicators corroborate the hostile intent: the ESM twin dist/index.mjs is clean while only the CJS main is tampered; the package advertises itself as a Vite plugin but the shipped code is an unrelated MobX-style store plus a MySQL-flavored DivbloxDatabaseConnector cover-story class; and dist/index.js pulls in an undeclared 'oubliette' dependency while the bytecode requires an undeclared 'axios', both consistent with attacker scaffolding to complete the exec chain via name-squat or hoist collision.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

50d2f5d3fe93de908c3da2d129b5b766a740b16a0eebf6c29c684605a9eaccf3

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-plugin-model (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-plugin-model across your stack and pipelines.
If you installed it — respond
Remove vite-plugin-model from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vite-plugin-model 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 vite-plugin-model 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. vite-plugin-model on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010372

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vite-plugin-model-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring