Malicious Code Injection in zul-semur41-riris: A Threat to npm Users

zul-semur41-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93044: Malicious code in zul-semur41-riris (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 'zul-semur41-riris' is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'zul-semur41-riris' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants. This behavior can compromise the integrity of the npm registry and potentially expose users to further malicious activities.

How To Fix

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

npm uninstall zul-semur41-riris

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 package from your project by running the following command: npm uninstall zul-semur41-riris. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The 'zul-semur41-riris' package presents a significant threat to npm users due to its malicious behavior. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities. Staying informed and proactive can help safeguard your applications from potential risks.

See every vulnerability recorded for zul-semur41-riris →

Share this vulnerability

FAQ

The 'zul-semur41-riris' package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of derivative packages.

This vulnerability can lead to the modification of your package.json file, potentially exposing your project to further malicious activities and cluttering the npm registry.

If you have installed 'zul-semur41-riris', it is crucial to uninstall it immediately and monitor your project for any other vulnerabilities.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor and alert you in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall zul-semur41-riris

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