Malicious Code Exploit in arrogant_wildcat-silentdev Package

arrogant_wildcat-silentdev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99611: Malicious code in arrogant_wildcat-silentdev (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 arrogant_wildcat-silentdev package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications that depend on these packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the arrogant_wildcat-silentdev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, increased risk of dependency confusion, and exposure of applications to untrusted code. The malicious payload can compromise the security of applications relying on this package, making it critical to address.

How To Fix

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

npm uninstall arrogant_wildcat-silentdev

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 arrogant_wildcat-silentdev package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json using tools like Vulert to receive real-time alerts for any open-source vulnerabilities in your software.

Conclusion

The arrogant_wildcat-silentdev package contains malicious code that poses significant risks to applications using it. It is crucial to remove this package and monitor for any vulnerabilities using tools like Vulert to ensure the security of your software.

See every vulnerability recorded for arrogant_wildcat-silentdev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the creation and publication of derivative packages.

The vulnerability can lead to the introduction of untrusted code into your application, potentially compromising its security and integrity.

You should remove the arrogant_wildcat-silentdev package from your project and monitor for any updates or patches.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities and alerts you in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

npm uninstall arrogant_wildcat-silentdev

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