Malicious Code Injection in clararodrigues Package: npm Vulnerability Overview

clararodrigues Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171044: Malicious code in clararodrigues (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 clararodrigues 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 exploits npm's publishing mechanisms, leading to potential security risks for developers and their applications.

Vulnerability Detail

The clararodrigues package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious payload continuously republishes variants of the package, polluting the npm registry and potentially compromising the integrity of dependent applications.

How To Fix

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

npm uninstall clararodrigues

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 measure, avoid using the clararodrigues package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure no malicious packages are included.

Conclusion

The clararodrigues package poses a significant security risk due to its malicious code that alters package configurations and republishing behavior. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for clararodrigues →

Share this vulnerability

FAQ

The clararodrigues package is an npm package used in JavaScript development, but it has been identified as malicious.

The malicious code can compromise your application's integrity by modifying essential files and republishing variants, which can lead to security vulnerabilities.

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

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall clararodrigues

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