Malicious Code Vulnerability in damaged_moth_0xrequest Package

damaged_moth_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101195: Malicious code in damaged_moth_0xrequest (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 damaged_moth_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious payload embedded within the damaged_moth_0xrequest package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The continuous republishing of these variants can disrupt the ecosystem and potentially harm developers relying on legitimate packages.

How To Fix

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

npm uninstall damaged_moth_0xrequest

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 measure, you can avoid using the damaged_moth_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The damaged_moth_0xrequest package contains a significant vulnerability due to its malicious code, which can compromise the integrity of the npm registry. It is vital to remove this package from your project and monitor for any vulnerabilities using tools like Vulert.

See every vulnerability recorded for damaged_moth_0xrequest →

Share this vulnerability

FAQ

The damaged_moth_0xrequest package is an npm package involved in the tea.xyz token reward campaign, designed to automate the generation and publication of packages.

The malicious code modifies your package.json file, potentially removing important flags and altering version numbers, which can lead to the pollution of the npm registry.

Currently, there is no patched version available for the damaged_moth_0xrequest package. It is recommended to uninstall it immediately.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application at Vulert Scanner.

If you have used the damaged_moth_0xrequest package, it is crucial to uninstall it and check for any dependencies that may be affected. Consider using alternative packages.

How To Fix

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

npm uninstall damaged_moth_0xrequest

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