Malicious Code Injection in valentinamonteiro Package - npm Vulnerability

valentinamonteiro Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171976: Malicious code in valentinamonteiro (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 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 valentinamonteiro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that have randomized names. This behavior not only affects the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in the valentinamonteiro package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of packages that include scripts designed to automatically publish derivative versions with altered package.json files. These scripts remove private flags, change version numbers, and generate random package names, which can lead to a polluted npm registry. The ramifications include potential security risks for developers who may inadvertently install these malicious packages, compromising their applications and systems.

How To Fix

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

npm uninstall valentinamonteiro

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 avoid using the valentinamonteiro package altogether. If it is already included in your project, you can remove it by executing the following command: npm uninstall valentinamonteiro. Additionally, consider using a tool like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The valentinamonteiro package poses a significant security risk due to its association with a malicious campaign that exploits the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive is key to maintaining the security of your applications.

See every vulnerability recorded for valentinamonteiro →

Share this vulnerability

FAQ

The valentinamonteiro package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code can modify your package.json file, remove private flags, and publish derivative packages, potentially compromising your application's security.

You should uninstall the valentinamonteiro package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert to check your package-lock.json file for vulnerabilities without needing to install any software.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest versions.

How To Fix

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

npm uninstall valentinamonteiro

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