Critical Malicious Code Vulnerability in itobuz-angular Package

itobuz-angular Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190971: Malicious code in itobuz-angular (npm). Affects itobuz-angular versions 0.0.1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The itobuz-angular package is a JavaScript library designed for use in Angular applications, providing various functionalities to enhance user interfaces. However, it has been identified to contain malicious code that poses significant security risks to systems using it. This vulnerability compromises the integrity of the application and can lead to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the itobuz-angular package. This code can fully compromise any computer that has the package installed or running, allowing attackers to gain control over the system. The ramifications include potential data theft, unauthorized access to sensitive information, and the installation of additional malicious software. Users are advised to treat any system with this package as compromised and take immediate action to secure their data.

How To Fix

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

npm uninstall itobuz-angular

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, you can temporarily disable the functionalities that rely on the itobuz-angular package until it is removed or a secure version is released. Additionally, ensure that your system is monitored for any unusual activities that may arise from the malicious code.

Conclusion

The itobuz-angular package has been identified as containing malicious code that poses serious security risks. Users are strongly urged to remove the package and secure their systems immediately. Continuous monitoring and vigilance are essential to protect against such vulnerabilities.

See every vulnerability recorded for itobuz-angular →

Share this vulnerability

FAQ

Immediately remove the package and rotate all sensitive keys and secrets stored on the affected system.

You can use the Vulert platform to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check your application without any signup.

Currently, there is no patched version available. It is advised to remove the package entirely.

Failure to address this vulnerability can lead to unauthorized access, data breaches, and further compromise of your system.

It is advisable to exercise caution and monitor for updates regarding the package. Always verify the integrity of packages before installation.

How To Fix

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

npm uninstall itobuz-angular

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