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

vite-config-fieldnpm

vite-config-field is a confirmed malicious npm package (MAL-2026-5936) that typosquats a legitimate package to trick installs (malicious versions 1.1.0, 1.1.1, 1.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-config-field (npm)

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

What this malware does

[email protected] impersonates the legitimate vite-plugin-pwa package (README copies its banner/badges, funding field points at antfu's GitHub Sponsors, and the package re-exports VitePWA alongside the attacker-introduced configFields helper). The ESM entry dist/index.js exposes a configFields(userOpt) function which, when called from a Vite config (as the README instructs), detached-spawns node dist/client/dev/reactopt.js with stdio ignored and unref'd to hide the child from the developer. dist/client/dev/reactopt.js (lines 21-23) fetches https://www.jsonkeeper.com/b/DDC6J with header x-secret-key: _, reads the response's data.Cookie field, and executes it via new Function.constructor('require', params); handler(require) — granting the attacker arbitrary Node code execution with require injected, on any developer or build machine that imports the package and invokes configFields(). The CJS entry dist/index.cjs intentionally omits this payload, so reviewers inspecting main see clean code while modern ESM toolchains that resolve via module/import get the dropper. The fetched payload host (jsonkeeper.com) is a mutable public paste-bin-like service, so the executed code can change at any time.

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

6 flagged
1.1.01.1.11.1.21.1.31.1.41.1.5

Indicators of compromise (SHA-256)

d52d1d84d7572baf6a74539864b64d5b5c803f828fc82a1dae4de2dfebdb986f
6032e3a166468dfea9d563751babb56c0684245524dfa2a284263c1acdef1dbc
8e5dabbc9cf746e153391fbe76f4dc54f9bccb9f7fd467d5b80d07c84ab1fb58
9f3a3a13cccda063a98a0048217c3db7c09659ba943668736368cfff187ad4b4
09ca3b3a4ccc455ace29b57fedf8a00d62b70a105677dc21490550d608675b7b
eb9b02255137b2214d4856b7c6f85776d862c07ae78c94787c013a4851afe0e2
d23dc727c467b5dd7cb7823454ed195f74b414c27db19cea2afb724225c03f74
2ba7447f7b684facc0a16568bb3fdca4dc571c16481a8fc563ae94525ef94132

Detection & response playbook

Typosquat
  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-field (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-config-field across your stack and pipelines.

  2. If you installed it — respond

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

  3. Did it already run?

    If vite-config-field 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-field 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-field on npm has been identified as a malicious package (versions 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006846IN-MAL-2026-006873IN-MAL-2026-006872GHSA-w8vm-43w2-4xqfIN-MAL-2026-009205IN-MAL-2026-009389IN-MAL-2026-009390

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

vite-config-field (npm) malicious package — MAL-2026-5936 | O3 Security