Which versions of prezdentkxheiw are malicious?

The following npm versions of prezdentkxheiw are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate prezdentkxheiw if I installed it?

prezdentkxheiw is a typosquat — you almost certainly intended a legitimately-named package. Remove prezdentkxheiw, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed prezdentkxheiw — how do I know if it already compromised me?

If prezdentkxheiw 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 prezdentkxheiw part of a known attack campaign?

Yes — prezdentkxheiw is associated with the GHSA-943h-xm4q-hpg6, IN-MAL-2026-017416, IN-MAL-2026-017489 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 prezdentkxheiw 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 prezdentkxheiw (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prezdentkxheiw across your stack and pipelines.

Malicious package

prezdentkxheiwnpm

prezdentkxheiw is a confirmed malicious npm package (MAL-2026-13833) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in prezdentkxheiw (npm)

MAL-2026-13833

Immediate action

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

npm uninstall prezdentkxheiw

What this malware does

The package contains only index.html (declared as main) and package.json. The HTML impersonates a Cloudflare 'Just a moment...' challenge and includes an obfuscator.io-style script whose onTurnstileComplete handler reconstructs a target URL from an encoded string array (_0x2885) and calls window.location.replace to redirect the browser. There are no preinstall/install/postinstall/prepare lifecycle hooks, no JavaScript entrypoint, and the declared main is an HTML file that Node cannot execute via require. Installing or requiring this package does not run code on the installer's machine. The artifact is abuse of the npm registry as static hosting for a phishing/redirect landing page aimed at browser visitors (e.g. via a CDN like unpkg), not a supply-chain attack against installers.

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)

a8b5a4cf417116380c0eb9a942f6dc7b39dbec1a19cf1537bd58d377616040ae

b524c1b4d84ba3f109eddb254753a02dac72fa61397c4f03dbcbb814c6aaa68f

aca256766f0d7007671907e52cc47df419800bbcf72ba901646376ad87b6bd9f

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 prezdentkxheiw (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prezdentkxheiw across your stack and pipelines.
If you installed it — respond
prezdentkxheiw is a typosquat — you almost certainly intended a legitimately-named package. Remove prezdentkxheiw, 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 prezdentkxheiw 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 prezdentkxheiw 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. prezdentkxheiw 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

GHSA-943h-xm4q-hpg6IN-MAL-2026-017416IN-MAL-2026-017489

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks prezdentkxheiw-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