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

vera-kupang69-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110397: Malicious code in vera-kupang69-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 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 vera-kupang69-ruro package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate the npm registry for fraudulent purposes, including inflating developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the vera-kupang69-ruro package stems from its malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, thereby republishing variants to pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's package management system for malicious intent. The ramifications include potential security risks for developers who unknowingly install this package, leading to compromised systems and reputational damage.

How To Fix

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

npm uninstall vera-kupang69-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-kupang69-ruro package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies using tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time.

Conclusion

The vera-kupang69-ruro package poses a significant threat to npm users due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for vera-kupang69-ruro →

Share this vulnerability

FAQ

The vera-kupang69-ruro package is an npm package linked to a token reward campaign that has been identified as malicious.

The malicious code modifies your package.json file, potentially compromising your project's integrity and security.

You should uninstall the package immediately using npm uninstall vera-kupang69-ruro and check for any other affected dependencies.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall vera-kupang69-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