Malicious Code Injection in irma-getuk2-ruro Package

irma-getuk2-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104389: Malicious code in irma-getuk2-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-getuk2-ruro package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate the development and management of web applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the irma-getuk2-ruro package stems from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to trust the integrity of packages and potentially exposing applications to further vulnerabilities.

How To Fix

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

npm uninstall irma-getuk2-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 irma-getuk2-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your project's dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The irma-getuk2-ruro package poses a significant security risk due to its malicious behavior of modifying package files and republishing harmful variants. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for irma-getuk2-ruro →

Share this vulnerability

FAQ

The irma-getuk2-ruro package is an npm package used in JavaScript applications, but it has been identified as malicious due to its involvement in a token reward scheme.

This vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package.json and republishing harmful variants.

If you have installed the irma-getuk2-ruro package, it is crucial to remove it from your project immediately and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, providing alerts for any issues.

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 irma-getuk2-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