Which versions of itobuz-angular-auth are malicious?

The following npm versions of itobuz-angular-auth are flagged malicious: 8.0.11. Treat any of these as compromised.

How do I remediate itobuz-angular-auth if I installed it?

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

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

Yes — itobuz-angular-auth is associated with the GHSA-6c53-64xr-m4p9 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 itobuz-angular-auth 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 itobuz-angular-auth (version 8.0.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging itobuz-angular-auth across your stack and pipelines.

Malicious package

itobuz-angular-authnpm

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

MAL-2025-190972

Immediate action

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

npm uninstall itobuz-angular-auth

What this malware does

The package itobuz-angular-auth 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

8.0.11

Indicators of compromise (SHA-256)

93a90437db64a4e66a1233c643d625bab786c14470c9d5ba56dfaa10daa03bc3

afed61db59aa59cee728d1b2cbe413a85ae32a192004efad9e9d126770433bdf

817a3f1a95ec563a267b5eba52e8e010b687d04ee4ea01217dbc1a0566605214

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

Campaign

GHSA-6c53-64xr-m4p9

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks itobuz-angular-auth-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