exam-kitnpm
exam-kit is a confirmed malicious npm package (MAL-2026-14331) that executes malicious code on install (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in exam-kit (npm)
What this malware does
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.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for exam-kit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging exam-kit across your stack and pipelines.
If you installed it — respond
Remove exam-kit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If exam-kit 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.
How O3 protects you
O3 blocks exam-kit 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks exam-kit-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.