Malicious code in exam-kit (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14331
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (29cd95c1b59238861675a30a947648a2280420c11e53dcb4f8501db5cb736313) On any require/import of exam-kit, the main entry runs a top-level await that reads an out-of-package file at../../../../public/logo.ico, DES-decrypts it using a hardcoded key ('bf497c0b9cee'), and pipes the plaintext into a detached `node` child process via stdin (spawn('node', [], {detached:true, stdio:['pipe','ignore','ignore']}); stdin.write(rsaDecrypted); unref()). The decrypted bytes are opaque code executed on the installer's host with no integrity check. The loader hides its purpose with cover-story naming: a variable named `rsaDecrypted` actually holds DES-decrypted content, the function `readLogoIco` treats an.ico asset as ciphertext, and errors are logged as 'ThetaSDK initialization error' — unrelated to the package's stated exam-session purpose. The path-traversal source (../../../../public/logo.ico), hardcoded symmetric key, misleading log strings, and detached/unref'd spawn are dropper-loader characteristics rather than legitimate library behavior. ## Source: ghsa-malware (e817468936bfd06bc41640b486d0d044e5934bb8e7653bd97340efd4920d8b7a) 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.
- Source published
- 20 Aug 2026 18:15:34 UTC
- Source modified
- 20 Aug 2026 22:01:44 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.