NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

vite-json-confignpm

Advisory published Updated

vite-json-config is a confirmed malicious npm package (MAL-2026-4705) that opens a backdoor for remote access (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-json-config (npm)

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

What this malware does

The package presents itself as a vite/tsconfig path helper and clones the public API of tsconfig-paths (createMatchPath, matchFromAbsolutePaths, register, loadConfig). A new exported configJson entry point spawns a detached node lib/mapProps.js child process via child_process.spawn(..., { detached: true, stdio: 'ignore' }) (lib/config-loader.js). lib/mapProps.js performs an HTTPS GET to https://www.jsonkeeper.com/b/5IZTJ — an anonymous, mutable JSON paste host — and passes the response's Cookie field directly to new Function('require', s)(require), giving the publisher arbitrary code execution inside the consumer process with full require access. The fetch URL and header are concealed by shadowing process with a local object whose env uses cover-story names (DEV_API_KEY, DEV_SECRET_KEY, DEV_SECRET_VALUE) that actually hold the C2 URL and HTTP header. There is no integrity check on the fetched payload; the paste content can be changed at any time by whoever controls the jsonkeeper.com entry. Combined with the cloned legitimate-package API surface, this is a deliberate supply-chain dropper, not a coding mistake.

Malicious versions

1 flagged
1.0.5

Indicators of compromise (SHA-256)

9a7c9683fed8b8696938eb7ad88e158f70a075851b0dd511af991ecd69a4d0fd

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for vite-json-config (version 1.0.5).

  2. If you installed it — respond

    vite-json-config 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.

  3. Did it already run?

    If vite-json-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. vite-json-config on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003611

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks vite-json-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

vite-json-config (npm) malicious package — MAL-2026-4705 | O3 Security