Malicious Code Injection in vera-rawon41-ruro Package: A Threat to npm Users

vera-rawon41-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110409: Malicious code in vera-rawon41-ruro (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 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 vera-rawon41-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify essential files and publish variants that can mislead developers and inflate reputation scores.

Vulnerability Detail

The vulnerability originates from the vera-rawon41-ruro package, which is linked to the tea.xyz token reward campaign. It contains scripts designed to automatically generate and publish derivative packages with randomized names. The malicious payload alters the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior can lead to pollution of the npm registry, making it difficult for developers to trust the integrity of packages and potentially exposing them to further security risks.

How To Fix

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

npm uninstall vera-rawon41-ruro

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 vera-rawon41-ruro package and monitor your project's dependencies for any signs of malicious activity. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The vera-rawon41-ruro package poses a significant threat to npm users due to its malicious code that alters package files and floods the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the security of your projects.

See every vulnerability recorded for vera-rawon41-ruro →

Share this vulnerability

FAQ

The vera-rawon41-ruro package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages and potentially exposing your project to further security risks.

You should uninstall the vera-rawon41-ruro package immediately and monitor your dependencies for any malicious activity.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay updated on security advisories related to the packages you use.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring access to your code.

How To Fix

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

npm uninstall vera-rawon41-ruro

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