Malicious Code Injection in erwin-botok9-ruro: A Threat to npm Ecosystem

erwin-botok9-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102198: Malicious code in erwin-botok9-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 package erwin-botok9-ruro is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in erwin-botok9-ruro originates from its inclusion in a malicious campaign that uses autopublish scripts to manipulate package.json files. This manipulation involves removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to a significant pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the integrity of their applications.

How To Fix

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

npm uninstall erwin-botok9-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 workaround, you can remove the erwin-botok9-ruro package from your project by executing the following command: npm uninstall erwin-botok9-ruro. This will prevent any malicious code from executing while you seek a more permanent solution.

Conclusion

The erwin-botok9-ruro package poses a significant threat due to its malicious code designed to manipulate npm packages. It is crucial for developers to stay informed about such vulnerabilities and take immediate action to protect their applications by updating or removing affected packages.

See every vulnerability recorded for erwin-botok9-ruro →

Share this vulnerability

FAQ

erwin-botok9-ruro is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the injection of malicious code, which may compromise your application's integrity and security.

You should uninstall the package immediately and check for any updates or patches that may be available.

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

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

How To Fix

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

npm uninstall erwin-botok9-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