Malicious Code Injection in erwin-dodol54-ruro: A Threat to npm Packages

erwin-dodol54-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102199: Malicious code in erwin-dodol54-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package erwin-dodol54-ruro is part of a larger ecosystem within npm, primarily used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit npm's package management system. The campaign involves the creation of numerous derivative packages that are designed to inflate developer reputation scores through automated publishing scripts. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability originates from the erwin-dodol54-ruro package, which is linked to the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to security risks for applications that depend on these packages. The ramifications include unauthorized access, data breaches, and a compromised development environment.

How To Fix

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

npm uninstall erwin-dodol54-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 erwin-dodol54-ruro package and monitor your package-lock.json file for any unauthorized changes. You can also use tools like Vulert to monitor for vulnerabilities in your project without needing to access the code directly. For real-time alerts, visit the Vulert playground at https://vulert.com/scanner.

Conclusion

The erwin-dodol54-ruro package represents a significant threat within the npm ecosystem due to its malicious code designed to exploit the package management system. Developers should take immediate action to remove this package and monitor their projects for any related vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for erwin-dodol54-ruro →

Share this vulnerability

FAQ

The erwin-dodol54-ruro package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm ecosystem.

This vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.

You should uninstall the erwin-dodol54-ruro package immediately and check for any other potentially malicious packages in your project.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

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

How To Fix

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

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