Malicious Code Injection in irma-tek91-ruro Package - npm Vulnerability

irma-tek91-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104418: Malicious code in irma-tek91-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 irma-tek91-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages. Its functionality is compromised, as it is designed to manipulate package metadata and publish numerous derivative packages, ultimately affecting the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the irma-tek91-ruro package. This code is part of a broader scheme that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which pollutes the npm registry and can lead to security risks for developers relying on these packages.

How To Fix

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

npm uninstall irma-tek91-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 irma-tek91-ruro package and monitor your project for any dependencies that may have been affected by this malicious code. Regularly check your package-lock.json file for any unauthorized changes.

Conclusion

The irma-tek91-ruro package poses a significant security risk due to its malicious code designed to manipulate package metadata and publish unauthorized derivatives. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for irma-tek91-ruro →

Share this vulnerability

FAQ

The irma-tek91-ruro package is an npm package that has been identified as containing malicious code designed to manipulate package metadata.

This vulnerability can lead to the pollution of the npm registry and may compromise the security and integrity of your project by introducing unauthorized packages.

If you have installed the irma-tek91-ruro package, you should uninstall it immediately and check for any other affected packages in your project.

Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

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