Which versions of get-power are malicious?

The following npm versions of get-power are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate get-power if I installed it?

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.

I already installed get-power — how do I know if it already compromised me?

If get-power 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.

Is get-power part of a known attack campaign?

Yes — get-power is associated with the IN-MAL-2026-020044 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find get-power across my projects, lockfiles, and CI pipelines?

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

Malicious package

get-powernpm

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)

MAL-2026-16156

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall get-power

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.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

e261e4010770fc43fd02cf8c9add484ea5f8a92a21f60682f2aea73f0ce110f7

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for get-power (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging get-power across your stack and pipelines.
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 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.
How O3 protects you
O3 blocks get-power 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. get-power on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020044

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database