Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

knowledge-gradernpm

knowledge-grader is a confirmed malicious npm package (MAL-2026-12795) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in knowledge-grader (npm)

MAL-2026-12795
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall knowledge-grader

What this malware does

The package's preinstall hook runs index.js, which collects hostname, username, home directory, DNS servers, package path, and the contents of /etc/passwd and /etc/hosts, then HTTPS-POSTs the JSON payload to the hardcoded Burp Collaborator subdomain tebdjgz4guem6t74pf6iyowyjppgd71w.oastify.com. This fires automatically on npm install with no user interaction.

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

2 flagged
1.0.11.0.2

Indicators of compromise (SHA-256)

74d01af74706eee07fb8ed306ec3b830641f63b4c055d605026edff65fd11c8f
2de2d31bd044eb84689187958c0f7a03afa21e9d83ae6edb90e3c796ac5d09dd
2f06ec516f900a6ad0a2b981cd7002a021a232e1c9cb58fe2298da4c713fcea8

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for knowledge-grader (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging knowledge-grader across your stack and pipelines.

  2. If you installed it — respond

    Remove knowledge-grader 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.

  3. Did it already run?

    If knowledge-grader 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.

  4. How O3 protects you

    O3 blocks knowledge-grader 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

No. knowledge-grader on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014949GHSA-m4g7-2mxw-5m83IN-MAL-2026-019826

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks knowledge-grader-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.

Explore

knowledge-grader (npm) malicious package — MAL-2026-12795 | O3 Security