Malicious Code Exposure in iwan-lodeh83-ruro Package: npm Vulnerability

iwan-lodeh83-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104459: Malicious code in iwan-lodeh83-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 iwan-lodeh83-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 inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses a risk to developers using affected packages.

Vulnerability Detail

The vulnerability originates from the iwan-lodeh83-ruro package, which is involved in the tea.xyz token reward campaign. It contains scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload can also lead to potential security risks if developers unknowingly use these compromised packages in their applications.

How To Fix

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

npm uninstall iwan-lodeh83-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, avoid using the iwan-lodeh83-ruro package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for any open-source vulnerabilities.

Conclusion

The iwan-lodeh83-ruro package poses a significant risk due to its malicious code designed to manipulate package configurations and pollute the npm registry. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your software.

See every vulnerability recorded for iwan-lodeh83-ruro →

Share this vulnerability

FAQ

The iwan-lodeh83-ruro package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies package configurations and pollutes the npm registry.

If you have installed the iwan-lodeh83-ruro package, you should uninstall it immediately using 'npm uninstall iwan-lodeh83-ruro'.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file. You can check your application using the Vulert playground without any signup.

Yes, consider using other reputable npm packages that provide similar functionality without the associated risks of malicious behavior.

How To Fix

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

npm uninstall iwan-lodeh83-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