Malicious code in hfkcdyuwbdx1 (npm)
MAL-2026-13812 · GHSA-6px9-6xh2-4ggc
Published · Modified
Dependency scanning
Check whether hfkcdyuwbdx1 is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (5c3d2f214c9d9ba8dcc912ba18272665044c75eb18d8335c18b959687d45cbdb)
Package hfkcdyuwbdx1@1.0.0 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.
Source: ghsa-malware (a2011b6d175f4aaa7fed50737dcfbc8c8d194020a4010360c830a95e676b4d65)
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.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes