Critical Malicious Code Vulnerability in generator-ng-itobuz Package

generator-ng-itobuz Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191102: Malicious code in generator-ng-itobuz (npm). Affects generator-ng-itobuz versions 0.0.15. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The generator-ng-itobuz package is an npm tool designed for scaffolding Angular applications. It provides developers with a streamlined way to set up new projects with predefined configurations and templates. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the generator-ng-itobuz package. This code can compromise the entire system, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of this code means that any computer running this package should be considered fully compromised, with potential ramifications including data theft and system manipulation.

How To Fix

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

npm uninstall generator-ng-itobuz

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

Currently, there are no effective workarounds to mitigate the risks posed by this malicious package. The best course of action is to uninstall the package and secure your system.

Conclusion

The generator-ng-itobuz package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of your packages using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for generator-ng-itobuz →

Share this vulnerability

FAQ

It is an npm package used for scaffolding Angular applications, providing templates and configurations for developers.

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

You should immediately uninstall the generator-ng-itobuz package and rotate any sensitive information stored on your system.

No, there is currently no patched version available for the generator-ng-itobuz package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.

How To Fix

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

npm uninstall generator-ng-itobuz

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