vite-json-pwanpm
vite-json-pwa is a confirmed malicious npm package (MAL-2026-6969) that opens a backdoor for remote access (malicious versions 1.1.1, 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vite-json-pwa (npm)
What this malware does
[email protected] impersonates the legitimate vite-plugin-pwa package (author metadata claims 'inna voik' while funding/homepage point at the real vite-pwa/antfu project) and re-exports its API alongside an added configField(...) middleware factory. When a consumer invokes configField (the expected pattern for a drop-in vite-plugin-pwa replacement), it spawns a detached, stdio-ignored node child running dist/client/dev/reactopt.js. That helper uses axios to GET https://www.jsonkeeper.com/b/J7GQS, extracts a Cookie field from the JSON body, and executes it via new Function('require', s)(require) — arbitrary attacker-controlled Node code with full privileges in the developer/build process tree. The remote URL is disguised inside a fake local process = { env: { DEV_API_KEY: 'https://www.jsonkeeper.com/b/J7GQS',... } } object to make the hardcoded C2 look like an env-var lookup, and the file/export names ('reactopt.js', 'configField') are cover-story identifiers designed to blend into a legitimate-looking build. jsonkeeper.com is a mutable public paste service, so the payload can be swapped at any time. The detached spawn plus stdio: 'ignore' and a retry loop are chosen to hide execution and ensure delivery.
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
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-json-pwa (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-json-pwa across your stack and pipelines.
If you installed it — respond
vite-json-pwa establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If vite-json-pwa 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-json-pwa 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
Detect & block this
O3 blocks vite-json-pwa-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.