Which versions of bgncvhferucfds are malicious?

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

How do I remediate bgncvhferucfds if I installed it?

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

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

Yes — bgncvhferucfds is associated with the GHSA-p783-m8pp-74w8, IN-MAL-2026-017486, IN-MAL-2026-017482 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 bgncvhferucfds 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 bgncvhferucfds (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bgncvhferucfds across your stack and pipelines.

Malicious package

bgncvhferucfdsnpm

bgncvhferucfds is a confirmed malicious npm package (MAL-2026-13784) 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 bgncvhferucfds (npm)

MAL-2026-13784

Immediate action

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

npm uninstall bgncvhferucfds

What this malware does

The package's sole content is a single obfuscated HTML file declared as main. When loaded in a browser, the page renders a fake Cloudflare Turnstile 'Just a moment...' verification screen, reconstructs a URL from string fragments that resolves to login.microsoft.com, and redirects the browser to that URL carrying the current page's query parameters. There are no lifecycle scripts, no JavaScript entry point, and the HTML is not executed by npm install or require(), so a developer installing the package is not directly attacked. The package abuses the npm registry (and its public CDN mirrors such as unpkg/jsDelivr) as free hosting for a Microsoft-credential phishing lure, using the Cloudflare-challenge cover story to bounce victims into an attacker-parameterized Microsoft login flow.

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)

af08b658efd69810d2d9c7b0109dd6e5d00640abf1501a237c8c5cc0fa4d880f

1eb215bc2902dfd37037e60905405a669f28ca8f7d8a45bc1f079cef4a610dd2

c1bf8639ccc5d2a70ae2e0ce754b76e1ca525699413f5d696289714005e86c57

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 bgncvhferucfds (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bgncvhferucfds across your stack and pipelines.
If you installed it — respond
bgncvhferucfds 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 bgncvhferucfds 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 bgncvhferucfds 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. bgncvhferucfds 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-p783-m8pp-74w8IN-MAL-2026-017486IN-MAL-2026-017482

References

Credits

Amazon Inspector · finder

Detect & block this

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