Which versions of jhkxcixudnvm1 are malicious?

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

How do I remediate jhkxcixudnvm1 if I installed it?

jhkxcixudnvm1 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — jhkxcixudnvm1 is associated with the GHSA-fm6c-v7f7-9q2g, IN-MAL-2026-017532, IN-MAL-2026-017536 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 jhkxcixudnvm1 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 jhkxcixudnvm1 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jhkxcixudnvm1 across your stack and pipelines.

Malicious package

jhkxcixudnvm1npm

jhkxcixudnvm1 is a confirmed malicious npm package (MAL-2026-13817) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jhkxcixudnvm1 (npm)

MAL-2026-13817

Immediate action

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

npm uninstall jhkxcixudnvm1

What this malware does

The package contains only package.json and index.html, with index.html declared as main. The HTML imitates a Cloudflare 'Just a moment...' verification interstitial and includes an obfuscated script that, after a short timeout, reconstructs a destination URL from a shuffled string array and redirects window.location to it, forwarding all current query parameters. No JavaScript executes at npm install time and require('jhkxcixudnvm1') does not run the redirect (the entry is HTML, not JS), so this version does not attack installers or build systems directly. The concern is registry abuse: npm is being used to host a Cloudflare-impersonating phishing/redirect page that would harm end-users if the tarball's index.html were fetched and opened in a browser (e.g., via a CDN that serves package contents). Recommend human review for a registry-abuse takedown rather than a supply-chain block, since installing or requiring the package produces no code execution, data exfiltration, or credential access on the installer.

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)

822b03ad5d841159d602cc18b9f300351daaeedcaa109bb4f027029d69e0da76

9fe30b2e3408aeba363ddae368a27a1089722d0a2876ea37a368f6c591ab5ce3

aecafeb32fc0bc6beb0fcd9f6cab36efa71c8e69dc966271eea55bd03ba8eadf

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jhkxcixudnvm1 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jhkxcixudnvm1 across your stack and pipelines.
If you installed it — respond
jhkxcixudnvm1 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If jhkxcixudnvm1 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 jhkxcixudnvm1 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. jhkxcixudnvm1 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-fm6c-v7f7-9q2gIN-MAL-2026-017532IN-MAL-2026-017536

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jhkxcixudnvm1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database