Malicious Code Vulnerability in irashi-21-re2ff: Exploitation of npm Packages

irashi-21-re2ff Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156887: Malicious code in irashi-21-re2ff (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 Your last release was probably never penetration tested 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 'irashi-21-re2ff' 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 aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package poses significant risks to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'irashi-21-re2ff' originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The package contains scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected projects but also pollutes the npm registry with numerous derivative packages, making it difficult for developers to identify legitimate packages.

How To Fix

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

npm uninstall irashi-21-re2ff

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 'irashi-21-re2ff' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'irashi-21-re2ff' package presents a significant security risk due to its malicious code designed to manipulate npm package management. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications and the npm ecosystem.

See every vulnerability recorded for irashi-21-re2ff →

Share this vulnerability

FAQ

The 'irashi-21-re2ff' package is an npm package identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json file and pollutes the npm registry with unwanted packages.

You should uninstall the 'irashi-21-re2ff' package immediately using 'npm uninstall irashi-21-re2ff' and check your package-lock.json for any remaining references.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time. You can use the Vulert playground to check for vulnerabilities without needing to sign up.

Currently, there is no specific patch for the 'irashi-21-re2ff' package. The best course of action is to remove the package and monitor for any updates.

How To Fix

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

npm uninstall irashi-21-re2ff

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