Malicious Code Injection in irashi-wew-sza: A Threat to npm Packages

irashi-wew-sza Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-156910: Malicious code in irashi-wew-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'irashi-wew-sza' 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, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous variants to inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'irashi-wew-sza' originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of malicious variants. This behavior not only pollutes the npm registry but also compromises the security of applications relying on this package, potentially allowing for unauthorized access or data manipulation.

How To Fix

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

npm uninstall irashi-wew-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 remove the 'irashi-wew-sza' package from your project by executing the command: 'npm uninstall irashi-wew-sza'. This will prevent any malicious activity associated with this package until a secure version is available.

Conclusion

The 'irashi-wew-sza' package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial to take immediate action by updating or removing the package to safeguard your applications.

See every vulnerability recorded for irashi-wew-sza →

Share this vulnerability

FAQ

The vulnerability involves malicious scripts that modify package metadata and republish variants, compromising the integrity of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As a temporary measure, you can uninstall the package using 'npm uninstall irashi-wew-sza' to mitigate risks until a secure version is released.

Yes, the vulnerability can lead to unauthorized access, data manipulation, and overall compromise of application security.

You can refer to the npm documentation and security advisories, or use tools like Vulert for real-time monitoring.

How To Fix

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

npm uninstall irashi-wew-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