Malicious Code Injection in xeric_wildcat_dumbs: A Threat to npm Ecosystem

xeric_wildcat_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111122: Malicious code in xeric_wildcat_dumbs (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 package 'xeric_wildcat_dumbs' is part of a larger set of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'xeric_wildcat_dumbs' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to confusion and misuse of legitimate packages. The origin of this vulnerability is linked to automated scripts that exploit the npm publishing process, making it a systemic issue within the ecosystem.

How To Fix

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

npm uninstall xeric_wildcat_dumbs

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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using the following command to audit your npm packages for vulnerabilities: npm audit.

Conclusion

The 'xeric_wildcat_dumbs' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying and republishing packages. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.

See every vulnerability recorded for xeric_wildcat_dumbs →

Share this vulnerability

FAQ

'xeric_wildcat_dumbs' is a malicious npm package that is part of a campaign to manipulate the npm registry by publishing fake packages.

This vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising your project's security.

You should immediately remove 'xeric_wildcat_dumbs' from your project and check for any unauthorized changes to your package.json file.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall xeric_wildcat_dumbs

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