Malicious Code Injection in notar-ucl-vibni Package - npm Vulnerability

notar-ucl-vibni Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163649: Malicious code in notar-ucl-vibni (npm). Affected versions are not published. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The notar-ucl-vibni package is part of the npm ecosystem, primarily utilized for various JavaScript applications. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This package has been identified as part of a larger scheme that aims to manipulate the npm registry by publishing numerous derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in the notar-ucl-vibni package stems from its association with a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious code is designed to automatically publish these variants, which can inflate developer reputation scores and potentially introduce security risks to applications relying on these packages.

How To Fix

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

npm uninstall notar-ucl-vibni

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 temporary workaround, you can remove the notar-ucl-vibni package from your project if it is not essential. Use the following command to uninstall it: npm uninstall notar-ucl-vibni. Additionally, consider using alternative packages that do not have known vulnerabilities.

Conclusion

The notar-ucl-vibni package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to update or remove this package to protect your project from potential risks. Regular monitoring for vulnerabilities is recommended to ensure the safety of your software.

See every vulnerability recorded for notar-ucl-vibni →

Share this vulnerability

FAQ

The notar-ucl-vibni package is an npm package involved in token reward campaigns, which has been identified to contain malicious code.

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

You should update the package to the latest version or remove it from your project to mitigate the risk.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall notar-ucl-vibni

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