NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

tool-registry-scriptsnpm

Advisory published Updated

tool-registry-scripts is a confirmed malicious npm package (MAL-2026-12482) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tool-registry-scripts (npm)

MAL-2026-12482
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tool-registry-scripts

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. index.js collects host identifiers (os.hostname(), os.userInfo(), homedir, DNS servers, cwd, package.json contents) and reads /etc/passwd and /etc/hosts, then POSTs the resulting JSON over HTTPS to the hardcoded out-of-band collaborator subdomain lsh5x8dwumsekllw37kacgaqxh3cr2fr.oastify.com. The destination is a Burp Collaborator OOB endpoint unrelated to any documented package purpose, and execution is automatic at install time.

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.01.0.1

Indicators of compromise (SHA-256)

b635b8b6d257c079a0d0a9c06e37910b67f2e75d1e71dced264043624951ce06
0723c99e49b056e9d946985e6401afa50ee28e766b0e7e0993914f4ad3538723
9e0602404e2a557346512f6e8f03f4fa11eaef5aaee3007fb3ebea692bead2fa
932ac67140a95e44a586a48985c17914b7c5319c4aef02c829dbf0f2fa2c19c2

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for tool-registry-scripts (2 malicious versions).

  2. If you installed it — respond

    Remove tool-registry-scripts 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 tool-registry-scripts was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-014861GHSA-r8mg-hv3j-fc44IN-MAL-2026-019788RLMA-2026-10801

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks tool-registry-scripts-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

tool-registry-scripts (npm) malicious package — MAL-2026-12482 | O3 Security