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

test-dev-bootnpm

test-dev-boot is a confirmed malicious npm package (MAL-2026-11488) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-dev-boot (npm)

MAL-2026-11488
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall test-dev-boot

What this malware does

On require/import (and when invoked as a bin), the package's main entrypoint detects Windows and installs an HKCU\Software\Microsoft\Windows\CurrentVersion\Run entry named 'WindowsAutoUpdate' that points at a launcher.vbs staged above the package root via wscript.exe, providing auto-start persistence on every user login. In the same import-time flow it fires background tasks sendExtInfo() and createAndSaveArchive() (host recon + archive-and-upload grabber) sourced from the declared sibling dependencies test-dev-host and test-dev-sync, which the local module re-exports and invokes (main, handleConnection, mainLoop, sendExtInfo, createAndSaveArchive). All errors are silently swallowed and the persistence value name is chosen to look like a Windows update task, hiding the behavior from the developer installing the package.

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

1 flagged
0.1.0

Indicators of compromise (SHA-256)

3cb67b63654219a5c04c8be6821fe3faad301c009b20e558f3a17aab0b85ef97
1fd45eccde1d78006f2a808730aa4723756d255697ac1479d52aa7e89f792e51

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 test-dev-boot (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-dev-boot across your stack and pipelines.

  2. If you installed it — respond

    Remove test-dev-boot 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 test-dev-boot 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 test-dev-boot 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. test-dev-boot on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fxj3-2jph-p7mgIN-MAL-2026-011188

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks test-dev-boot-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

test-dev-boot (npm) malicious package — MAL-2026-11488 | O3 Security