Malicious Code Injection in iwan-sroto31-ruro Package - npm Vulnerability

iwan-sroto31-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104481: Malicious code in iwan-sroto31-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-sroto31-ruro package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the iwan-sroto31-ruro package, which includes scripts that modify the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish variants, polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may introduce unwanted code into their applications.

How To Fix

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

npm uninstall iwan-sroto31-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 avoid using the iwan-sroto31-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.

Conclusion

The iwan-sroto31-ruro package poses a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain secure applications.

See every vulnerability recorded for iwan-sroto31-ruro →

Share this vulnerability

FAQ

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

If your application uses the iwan-sroto31-ruro package, it may introduce malicious code that can compromise your application's security and integrity.

You should uninstall the iwan-sroto31-ruro package immediately and check your application for any potential security issues.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, 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 iwan-sroto31-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