Malicious Code Vulnerability in slwrxu-devapptea Package

slwrxu-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108849: Malicious code in slwrxu-devapptea (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 slwrxu-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards. The presence of such malicious code poses a significant risk to developers and users relying on the integrity of npm packages.

Vulnerability Detail

The vulnerability in the slwrxu-devapptea package originates from its inclusion in a campaign that generates and publishes derivative packages with randomized names. This malicious code modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. The ramifications include potential security risks for applications using this package, as well as damage to the reputation of developers and the npm ecosystem as a whole.

How To Fix

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

npm uninstall slwrxu-devapptea

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 temporarily avoid using the slwrxu-devapptea package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for vulnerabilities using tools like Vulert.

Conclusion

The slwrxu-devapptea package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your applications.

See every vulnerability recorded for slwrxu-devapptea →

Share this vulnerability

FAQ

The slwrxu-devapptea package is part of a token reward campaign that has been identified as malicious, flooding the npm registry with harmful packages.

The vulnerability can lead to the modification of your package.json file, potentially exposing your application to security risks and affecting its integrity.

You should uninstall the slwrxu-devapptea package immediately and monitor your project for any other potentially malicious packages.

Yes, tools like Vulert can help monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall slwrxu-devapptea

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