Malicious Code Injection in erick-bakwan94-ruro Package - npm Vulnerability

erick-bakwan94-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102162: Malicious code in erick-bakwan94-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 erick-bakwan94-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 npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the erick-bakwan94-ruro package. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, which are then continuously republished. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these malicious variants, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall erick-bakwan94-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 workaround, you can avoid using the erick-bakwan94-ruro package altogether. If it is already in use, remove it from your package.json and run npm install to clean up your dependencies. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The erick-bakwan94-ruro package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor for updates to ensure the security of your projects. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for erick-bakwan94-ruro →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

If your application uses the erick-bakwan94-ruro package, it may be at risk of installing malicious variants that can compromise security and stability.

Remove the erick-bakwan94-ruro package from your project and monitor for any updates or patches that may address this vulnerability.

Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the packages you use.

How To Fix

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

npm uninstall erick-bakwan94-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