Malicious Code Injection in irma-liwet25-ruro: A Threat to npm Ecosystem

irma-liwet25-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104397: Malicious code in irma-liwet25-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 package 'irma-liwet25-ruro' 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'irma-liwet25-ruro' originates from its association with the tea.xyz token reward campaign. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This malicious behavior can lead to the proliferation of harmful packages in the npm registry, potentially compromising the integrity of applications that depend on these packages.

How To Fix

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

npm uninstall irma-liwet25-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, you can avoid using the 'irma-liwet25-ruro' package altogether. If it is already included in your project, remove it by running the command: npm uninstall irma-liwet25-ruro.

Conclusion

The 'irma-liwet25-ruro' package poses a significant risk to the npm ecosystem due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant and remove this package from their projects to maintain the integrity of their applications.

See every vulnerability recorded for irma-liwet25-ruro →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to flood the npm registry with derivative packages, compromising the integrity of the ecosystem.

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

You should uninstall the package immediately using the command: npm uninstall irma-liwet25-ruro.

Currently, there are no patches available for the irma-liwet25-ruro package. It is recommended to remove the package from your project.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights.

How To Fix

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

npm uninstall irma-liwet25-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