Malicious Code Injection in xaver-lapis63-ruro Package

xaver-lapis63-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111065: Malicious code in xaver-lapis63-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 xaver-lapis63-ruro package is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the xaver-lapis63-ruro package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to pollution of the npm registry. The malicious payload is part of a broader scheme to exploit npm's publishing system, potentially affecting developers' reputations and the integrity of the npm ecosystem.

How To Fix

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

npm uninstall xaver-lapis63-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 temporary workaround, you can prevent the installation of the xaver-lapis63-ruro package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include this package in its dependencies.

Conclusion

The xaver-lapis63-ruro package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any potential vulnerabilities using tools like Vulert.

See every vulnerability recorded for xaver-lapis63-ruro →

Share this vulnerability

FAQ

The xaver-lapis63-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The malicious code can alter your package.json file, remove private flags, and generate random package names, potentially compromising your project's integrity and reputation.

You should uninstall the xaver-lapis63-ruro package immediately using 'npm uninstall xaver-lapis63-ruro' and check for any unauthorized changes in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check for vulnerabilities without any installation by visiting the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the xaver-lapis63-ruro vulnerability without requiring any signup.

How To Fix

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

npm uninstall xaver-lapis63-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