Which versions of react-vite-assert are malicious?

The following npm versions of react-vite-assert are flagged malicious: 1.4.1. Treat any of these as compromised.

How do I remediate react-vite-assert if I installed it?

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

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

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

Malicious package

react-vite-assertnpm

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

Malicious code in react-vite-assert (npm)

MAL-2026-5933

Immediate action

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

npm uninstall react-vite-assert

What this malware does

[email protected] executes attacker-controlled JavaScript whenever the package is imported. The main entry transitively loads src/features/extras/config.js, which runs a top-level async IIFE that issues an HTTPS GET to https://www.jsonkeeper.com/b/HXDNM, takes the data.config string from the response, wraps it with new Function('require', s), and invokes it with a createRequire(import.meta.url)-built require — granting the fetched code full Node.js access (filesystem, network, child_process, env). The fetch is retried up to 5 times. The remote URL and request headers are disguised by a fake local process shadow object whose keys are named DEV_API_KEY/DEV_SECRET_KEY/DEV_SECRET_VALUE, where DEV_API_KEY actually holds the paste URL and the other two hold a request header name/value — deliberate misdirection rather than configuration. jsonkeeper.com is an anonymous, mutable paste host: whoever controls /b/HXDNM can change the executed payload at any time without republishing the package. The combination of import-time auto-execution, anonymous mutable code source, eval of fetched bytes with full require, and cover-story variable naming is unambiguous supply-chain attack tradecraft.

Malicious versions

1 flagged

1.4.1

Indicators of compromise (SHA-256)

746aecfafda9a8f780b53ef40a5697875c52514dfa6ebb29306992ad06128395

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 react-vite-assert (version 1.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-vite-assert across your stack and pipelines.
If you installed it — respond
Remove react-vite-assert 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 react-vite-assert 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 react-vite-assert 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. react-vite-assert on npm has been identified as a malicious package (version 1.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006845

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database