Which versions of vite-pwa-config are malicious?

The following npm versions of vite-pwa-config are flagged malicious: 1.1.1, 1.1.2. Treat any of these as compromised.

How do I remediate vite-pwa-config if I installed it?

vite-pwa-config is a typosquat — you almost certainly intended a legitimately-named package. Remove vite-pwa-config, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed vite-pwa-config — how do I know if it already compromised me?

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

Yes — vite-pwa-config is associated with the IN-MAL-2026-009388, IN-MAL-2026-009397 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 vite-pwa-config 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 vite-pwa-config (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-pwa-config across your stack and pipelines.

Malicious package

vite-pwa-confignpm

Malicious code in vite-pwa-config (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10092

Immediate action

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

npm uninstall vite-pwa-config

What this malware does

Package vite-pwa-config impersonates the popular vite-plugin-pwa (antfu) — the README instructs users to import configJson from vite-plugin-pwa, and package metadata reuses that project's funding link, badges, and banner. When the exported configJson/configField is invoked from a project's vite.config, dist/index.cjs/index.mjs spawns a detached node child (stdio:"ignore", child.unref()) running the bundled dist/client/dev/viteopt.js. That helper fetches a JavaScript string from https://www.jsonkeeper.com/b/FNOBS via axios and passes it to new Function('require', s)(require), giving the anonymous remote endpoint arbitrary code execution in the developer's build environment with full require access. The remote URL is disguised behind a local process = { env: { DEV_API_URL:..., DEV_SECREDT:..., DEV_PREFIX:... } } shadow object to make the fetch look like ordinary env-driven configuration. Detached/silenced child spawning plus the cover-story env shim are deliberate evasion of casual review, and jsonkeeper.com is a mutable, anonymous paste host — today's content can be swapped for any payload at any time. This is a typosquat lure carrying an unpinned remote-fetch-and-eval dropper.

Malicious versions

2 flagged

1.1.11.1.2

Indicators of compromise (SHA-256)

bab1e251883a8eceecc27c935ed05352375d438c1efbbd8727f2b13a766409d0

b2218a7874aeff01d6bb41eb677af428f8864aec1a7979319a1be932d948da46

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-pwa-config (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-pwa-config across your stack and pipelines.
If you installed it — respond
vite-pwa-config is a typosquat — you almost certainly intended a legitimately-named package. Remove vite-pwa-config, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If vite-pwa-config 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-pwa-config 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-pwa-config on npm has been identified as a malicious package (versions 1.1.1, 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009388IN-MAL-2026-009397

References

Credits

Amazon Inspector · finder

Detect & block this

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