Critical Malicious Code Vulnerability in itobuz-angular-auth Package

itobuz-angular-auth Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190972: Malicious code in itobuz-angular-auth (npm). Affects itobuz-angular-auth versions 8.0.11. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The itobuz-angular-auth package is an npm library designed for authentication in Angular applications. It provides essential features for user authentication and session management, making it a popular choice among developers. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any application that utilizes it.

Vulnerability Detail

The vulnerability originates from the discovery of embedded malicious code within the itobuz-angular-auth package. This code can compromise the integrity of any computer running the package, allowing unauthorized access to sensitive data, including secrets and keys. The malicious nature of the code means that systems using this package should be considered fully compromised, necessitating immediate action to mitigate potential damage.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall itobuz-angular-auth

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, if immediate removal of the package is not feasible, consider isolating the affected application from sensitive data and monitoring network traffic for any suspicious activity. However, this is not a foolproof solution and should only be a temporary measure.

Conclusion

The itobuz-angular-auth package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Immediate removal of the package and rotation of sensitive information is essential to safeguard your systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for itobuz-angular-auth →

Share this vulnerability

FAQ

Itobuz-angular-auth is an npm package used for authentication in Angular applications, providing features for user management and session handling.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

Immediately remove the itobuz-angular-auth package and rotate all secrets and keys stored on the affected system.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

While isolating the package may provide temporary relief, it is not a secure solution. The best course of action is to remove the package entirely.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall itobuz-angular-auth

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback