Which versions of internal-auth-provider are malicious?

The following npm versions of internal-auth-provider are flagged malicious: 50.50.50. Treat any of these as compromised.

How do I remediate internal-auth-provider if I installed it?

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

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

Yes — internal-auth-provider is associated with the GHSA-w76m-ffcr-5rfm 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 internal-auth-provider 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 internal-auth-provider (version 50.50.50). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internal-auth-provider across your stack and pipelines.

Malicious package

internal-auth-providernpm

Malicious code in internal-auth-provider (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3261

Immediate action

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

npm uninstall internal-auth-provider

What this malware does

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-auth-provider package. The package description self-identifies as a 'security research package for dependency confusion audit', indicating deliberate deception.

The package internal-auth-provider was found to contain malicious code.

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

50.50.50

Indicators of compromise (SHA-256)

9b0b45d99f2f9fcef2b68ab24bfa6ca0d37a13f9ca343972df8541a59a0f4358

76a6ba942ecf9ea05ab48effb39c99f4fab5f4e605b9acbd71c76d7a2f993318

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

Campaign

GHSA-w76m-ffcr-5rfm

References

github.com

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks internal-auth-provider-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