Malicious Code Injection in xaver-semur82-ruro: A Threat to npm Packages

xaver-semur82-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111088: Malicious code in xaver-semur82-ruro (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 Penetration testing for web, API and mobile 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 xaver-semur82-ruro is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores for token rewards. However, it has been identified as malicious due to its ability to modify package.json files and republish variants with altered names and versions, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in xaver-semur82-ruro originates from its malicious design, which includes scripts that remove private flags from package.json, change version numbers, and generate random package names. This behavior can lead to significant ramifications, including the compromise of the npm registry's integrity, increased difficulty in finding legitimate packages, and potential security risks for developers who unknowingly use these malicious packages.

How To Fix

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

npm uninstall xaver-semur82-ruro

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 workaround, you can monitor your dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without requiring any signup.

Conclusion

The xaver-semur82-ruro package poses a significant threat due to its malicious code that alters package.json files and repopulates the npm registry with compromised packages. It is crucial for developers to take immediate action by removing this package and monitoring their dependencies to maintain the security of their projects.

See every vulnerability recorded for xaver-semur82-ruro →

Share this vulnerability

FAQ

xaver-semur82-ruro is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

This vulnerability can compromise the integrity of your project's dependencies, leading to potential security risks and difficulties in managing legitimate packages.

You should uninstall the xaver-semur82-ruro package immediately using 'npm uninstall xaver-semur82-ruro' and check for any other affected packages.

Regularly update your dependencies and use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall xaver-semur82-ruro

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