# MAL-2026-14331: Malicious code in exam-kit (npm)


- **Type:** Malicious package
- **Package:** `exam-kit` (npm)
- **Published:** 20 Aug 2026
- **Also known as:** GHSA-3g8c-37c3-75vv

## What is MAL-2026-14331?

MAL-2026-14331 is a malicious package in exam-kit, published on 20 Aug 2026. 

### Official description

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.

## What should I do about MAL-2026-14331?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14331 is a malicious package: exam-kit (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14331/ (Markdown: https://insights.sbomify.com/MAL-2026-14331/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14331

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14331/
Summaries are generated and may contain mistakes; the official description above is the record.