get-powernpm
Advisory published Updated
get-power is a confirmed malicious npm package (MAL-2026-16156) that typosquats a legitimate package to trick installs (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in get-power (npm)
What this malware does
get-power impersonates ljharb's get-proto utility (package.json declares author 'Jordan Harband [email protected]' and homepage github.com/ljharb/get-power) while mirroring get-proto's file layout as cover. On require(), index.js base64-decodes two bundled files disguised as sourcemaps (parse.ts.map, init.ts.map) into parsetmp.js and config.js, require()s parsetmp.js, then fs.unlink()s all four files to erase traces. The decoded payload fetches an AES-256-CBC encrypted blob from https://www.jsonkeeper.com/b/V6NBX via axios, decrypts it with a hardcoded password/salt, and eval()s the plaintext. Whoever controls that paste has arbitrary code execution on any host that installs and loads 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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for get-power (version 1.0.3).
If you installed it — respond
get-power is a typosquat — you almost certainly intended a legitimately-named package. Remove get-power, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If get-power 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks get-power-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.