Malicious Code Injection in irashi-2a-a: A Threat to npm Packages
Summary
MAL-2025-156889: Malicious code in irashi-2a-a (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'irashi-2a-a' is part of the npm ecosystem and has been identified as a component of a malicious campaign targeting developers. It is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. This behavior compromises the integrity of the npm registry and can lead to widespread issues for developers relying on these packages.
Vulnerability Detail
The vulnerability in 'irashi-2a-a' originates from its involvement in the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, polluting the npm registry and potentially leading to security risks for 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 irashi-2a-aIf 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, consider using alternative packages that provide similar functionality without the associated risks. You can also lock your dependencies to specific versions that do not include the vulnerable package.
Conclusion
The 'irashi-2a-a' package poses a significant threat due to its malicious behavior, which can compromise the integrity of the npm registry and introduce security risks into applications. It is crucial for developers to remove this package and stay informed about potential updates or patches.
See every vulnerability recorded for irashi-2a-a →
FAQ
The vulnerability can lead to the pollution of the npm registry, making it difficult for developers to trust the packages they are using, and potentially introducing security risks into their applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without requiring any installation.
If you have installed 'irashi-2a-a', it is recommended to remove it immediately and check for any alternative packages that can fulfill your requirements.
Currently, there is no patched version available for 'irashi-2a-a'. It is advisable to monitor the package for any updates and remove it from your project.
Vulert uses the package-lock.json file to monitor and alert for open-source vulnerabilities in your software, providing real-time insights into potential risks.
