vite-react-toolkitnpm
vite-react-toolkit is a confirmed malicious npm package (MAL-2026-5701) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vite-react-toolkit (npm)
What this malware does
On import/require of vite-react-toolkit, src/features/extras/config.js (reached via the package main → createConfig.js → features/plugins.js side-effect import chain) fetches https://www.jsonkeeper.com/b/AAON3 with axios, extracts the response's .config field, and passes it to new Function('require', s)(require) — executing attacker-controlled JavaScript in the installer's Node.js process with full module-loading capability via createRequire(import.meta.url). The fetch retries 5 times and swallows errors silently; console.log is saved and restored around the call to suppress output from the injected code. The dropper URL is hidden behind a fake local process.env object whose keys are named DEV_API_KEY/DEV_SECRET_KEY/DEV_SECRET_VALUE to look like ordinary environment variable reads. The package advertises itself as a Vite configuration helper, which has no need for network I/O at import time. jsonkeeper.com is an anonymous, mutable paste host — the served bytes can change at any time without any change to the package — so the attacker controls what runs in every consumer's dev/build pipeline whenever this module is imported.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-react-toolkit (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-react-toolkit across your stack and pipelines.
If you installed it — respond
vite-react-toolkit 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 vite-react-toolkit 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-react-toolkit 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks vite-react-toolkit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.