my-empty-package (npm) · Malicious Code
Affects my-empty-packageSource GCVE Database
Malicious package : remove my-empty-package and rotate any secrets on hosts that installed it.
Data as of 28 Oct 2026, 19:28 UTC
Malicious package
Published to npm · OSV MAL-2026-10535
What to do
Remove my-empty-package from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmmy-empty-package | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The my-empty-package npm package version 1.0.0 contains malicious code that executes arbitrary platform-specific commands during installation. The install script runs different shell commands depending on the operating system, including obfuscated PowerShell commands on Windows, which is a common malware evasion technique. After execution, the package hides its malicious behavior by replacing the package manifest and deleting the install script, preventing detection. Although the current payload is benign (opening the calculator), the framework can execute any code with user privileges at install time, posing a serious risk.