Malicious Code Injection in xlorva-notthedevs Package: A Threat to npm Users

xlorva-notthedevs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111131: Malicious code in xlorva-notthedevs (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The xlorva-notthedevs package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been implicated in a malicious campaign associated with the tea.xyz token reward system. It is designed to automate the generation and publication of derivative packages, which can lead to significant issues in the npm registry and affect developers' reputations.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the xlorva-notthedevs package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload is designed to continuously republish these variants, effectively polluting the npm registry. This can lead to developers unintentionally using compromised packages, which may introduce security risks into their applications.

How To Fix

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

npm uninstall xlorva-notthedevs

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 avoid using the xlorva-notthedevs package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The xlorva-notthedevs package poses a significant threat to npm users due to its malicious code that modifies package files and repopulates the npm registry with compromised packages. It is crucial to take immediate action to remove this package and monitor your dependencies for security vulnerabilities.

See every vulnerability recorded for xlorva-notthedevs →

Share this vulnerability

FAQ

xlorva-notthedevs is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without needing to sign up.

Using this package can lead to the introduction of malicious code into your application, potentially compromising security and functionality.

It is recommended to regularly check for vulnerabilities, ideally as part of your development workflow, to ensure that you are using secure and up-to-date packages.

If you have used this package, you should uninstall it immediately and review your project for any other potentially compromised packages.

How To Fix

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

npm uninstall xlorva-notthedevs

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