Which versions of hfkcdyuwbdx1 are malicious?

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

How do I remediate hfkcdyuwbdx1 if I installed it?

hfkcdyuwbdx1 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 hfkcdyuwbdx1 — how do I know if it already compromised me?

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

Yes — hfkcdyuwbdx1 is associated with the GHSA-6px9-6xh2-4ggc, IN-MAL-2026-017540 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 hfkcdyuwbdx1 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 hfkcdyuwbdx1 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hfkcdyuwbdx1 across your stack and pipelines.

Malicious package

hfkcdyuwbdx1npm

hfkcdyuwbdx1 is a confirmed malicious npm package (MAL-2026-13812) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hfkcdyuwbdx1 (npm)

MAL-2026-13812

Immediate action

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

npm uninstall hfkcdyuwbdx1

What this malware does

Package [email protected] was scanned but produced no concrete findings from either rule-based checks or contextual code tracing. The package name is a random-looking alphanumeric string with no descriptive meaning, which is a common shape for throwaway/test/placeholder publications on npm. Without traced code evidence, no specific installer-harm mechanism (exfiltration, install-time fetch-and-execute, silent relay, credential distribution, backdoor) can be confirmed. Routing to human review so a reviewer can inspect the tarball contents and decide whether this is a benign placeholder, an abandoned test upload, or the start of a campaign.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a2011b6d175f4aaa7fed50737dcfbc8c8d194020a4010360c830a95e676b4d65

5c3d2f214c9d9ba8dcc912ba18272665044c75eb18d8335c18b959687d45cbdb

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 hfkcdyuwbdx1 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hfkcdyuwbdx1 across your stack and pipelines.
If you installed it — respond
hfkcdyuwbdx1 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 hfkcdyuwbdx1 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 hfkcdyuwbdx1 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. hfkcdyuwbdx1 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6px9-6xh2-4ggcIN-MAL-2026-017540

References

Credits

Amazon Inspector · finder

Detect & block this

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