CRITICAL npm Malware

Malicious code in @internal-infra/core-sso-bridge (npm)

MAL-2026-3256 · GHSA-67rg-vhjj-qrqq

Published · Modified

Dependency scanning

Check whether @internal-infra/core-sso-bridge 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

Dependency confusion and typosquatting campaign by threat actor "saif777". Packages use inflated version numbers (9999.9999.9999, 9999.9999.10000, 50.50.50, 7.66.5) to win version resolution in environments with private registries. All active packages execute a postinstall hook ("node index.js") that collects a system fingerprint — public IP (via api.ipify.org), username, hostname, CPU model, RAM, working directory, OS platform — and exfiltrates it as a Discord embed to a shared webhook (base64-obfuscated in source). Payloads include sandbox/bot detection: machines with ≤1 CPU or <2 GB RAM are flagged as sandbox/CI; real machines trigger a green embed. Targets organisations with a private @internal-infra/core-sso-bridge package.


__

Source: amazon-inspector (b56d1a8363c63432d0f638ee655cdd64d7e47dda5536694369fd7f3d4f29fcae)

The package @internal-infra/core-sso-bridge was found to contain malicious code.

Source: ghsa-malware (7cc74645a38c1c7eaaff059707a633d731297e8b83e37af5ea3a34ff37c92e50)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes