Which versions of basic-vite are malicious?

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

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

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

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

Yes — basic-vite is associated with the IN-MAL-2026-010892 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 basic-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 basic-vite (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 basic-vite across your stack and pipelines.

Malicious package

basic-vitenpm

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

Malicious code in basic-vite (npm)

MAL-2026-11131

Immediate action

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

npm uninstall basic-vite

What this malware does

package.json declares preinstall: node index.js, so npm install basic-vite auto-executes index.js. The script collects host identity data (hostname, username, home directory, DNS servers, current working directory, package.json contents) and reads /etc/passwd and /etc/hosts, then POSTs the collected payload over HTTPS to the hardcoded Burp Collaborator subdomain md3wko7hlcmvfsq16xh2higublhc53ts.oastify.com. The package name suggests a Vite-related utility, but no such functionality is present; the sole behavior is install-time data exfiltration to an attacker-controlled out-of-band interaction host.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ab736217e52ecd2e4aa966da6192e434d69f7d34cc5b7a1ce72c6c6ece6aff56

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 basic-vite (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 basic-vite across your stack and pipelines.
If you installed it — respond
basic-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 basic-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 basic-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. basic-vite 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-010892

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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