Malicious Code Injection in irashi-21-a: npm Package Vulnerability

irashi-21-a Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156884: Malicious code in irashi-21-a (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 irashi-21-a package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign that has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, its malicious nature poses significant risks to developers and users alike.

Vulnerability Detail

The vulnerability in the irashi-21-a package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially leading to reputation damage for developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall irashi-21-a

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 prevent the installation of the irashi-21-a package by using the following command to block it: npm install --no-save irashi-21-a. However, the best practice is to remove the package entirely.

Conclusion

The irashi-21-a package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security and integrity. Utilizing tools like Vulert can aid in identifying and mitigating these vulnerabilities effectively.

See every vulnerability recorded for irashi-21-a →

Share this vulnerability

FAQ

The irashi-21-a package is an npm package associated with a token reward campaign that generates and publishes derivative packages with malicious intent.

This vulnerability can lead to the pollution of the npm registry, potentially damaging your project's reputation and introducing security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

If you have installed the irashi-21-a package, you should uninstall it immediately using npm uninstall irashi-21-a.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities without requiring access to your code or installation.

How To Fix

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

npm uninstall irashi-21-a

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