Which versions of viteplugiin are malicious?

The following npm versions of viteplugiin are flagged malicious: 1.0.28. Treat any of these as compromised.

How do I remediate viteplugiin if I installed it?

viteplugiin is a typosquat — you almost certainly intended a legitimately-named package. Remove viteplugiin, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed viteplugiin — how do I know if it already compromised me?

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

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

Malicious package

viteplugiinnpm

Malicious code in viteplugiin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10546

Immediate action

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

npm uninstall viteplugiin

What this malware does

The npm package 'viteplugiin' impersonates '@base44/viteplugin' via a one-character insertion (doubled 'i') and ships a hostile payload in dist/index.js, the entry resolved by the package's exports map. After the legitimate-looking plugin code, a large whitespace gap conceals an obfuscated stub that uses Fisher-Yates string shuffles with hardcoded seeds to reconstruct the identifiers 'require', '__dirname', '__filename', 'undefined', and 'constructor', reassigns require/__dirname/__filename onto the global object, obtains the Function constructor, and invokes it on two decoded string bodies — executing attacker-controlled JavaScript at module load time in the consumer's Vite build. Because Vite configs import plugins at config-evaluation time, adding this plugin to vite.config.* causes the payload to run on developer and CI machines during any Vite command. Provenance is consistent with an attack drop: empty author field, no repository/homepage, and package.json 'main' pointing at a nonexistent root index.js while the exports map silently routes '.' to the tampered dist/index.js. The README and internal resolveId targets reference the legitimate '@base44/vite-plugin' as cover.

Malicious versions

1 flagged

1.0.28

Indicators of compromise (SHA-256)

5afbe0fab50b9582867bb208b6cfb20080849e27d27df79711f55e2db69f66bb

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for viteplugiin (version 1.0.28). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging viteplugiin across your stack and pipelines.
If you installed it — respond
viteplugiin is a typosquat — you almost certainly intended a legitimately-named package. Remove viteplugiin, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If viteplugiin 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 viteplugiin 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. viteplugiin on npm has been identified as a malicious package (version 1.0.28 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010390

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks viteplugiin-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