Malicious Code Injection in irashi-s-sza: npm Package Vulnerability

irashi-s-sza Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156900: Malicious code in irashi-s-sza (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-s-sza package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to further vulnerabilities and malicious activities.

How To Fix

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

npm uninstall irashi-s-sza

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-s-sza package by using the following command to uninstall it: npm uninstall irashi-s-sza. Additionally, consider using a package-lock.json file to lock your dependencies to known safe versions.

Conclusion

The irashi-s-sza package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for irashi-s-sza →

Share this vulnerability

FAQ

The irashi-s-sza package is an npm package associated with a token reward campaign that has been identified to contain malicious code.

The vulnerability can lead to the installation of compromised packages, which may introduce further security risks and malicious behavior in your application.

If you have installed the irashi-s-sza package, you should uninstall it immediately and monitor your application for any unusual behavior.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall irashi-s-sza

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