Malicious Code Detected in suspicious_badger_cyan-58: A Threat to npm Packages

suspicious_badger_cyan-58 Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109407: Malicious code in suspicious_badger_cyan-58 (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 package 'suspicious_badger_cyan-58' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the integrity of other packages and affecting developers' projects.

How To Fix

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

npm uninstall suspicious_badger_cyan-58

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, avoid using the 'suspicious_badger_cyan-58' package in your projects. Regularly audit your package dependencies for any malicious packages using tools like Vulert, which can monitor and alert you in real-time for open-source vulnerabilities.

Conclusion

The 'suspicious_badger_cyan-58' package poses a significant risk due to its malicious behavior aimed at inflating developer reputation scores. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for suspicious_badger_cyan-58 →

Share this vulnerability

FAQ

The main threat is that it modifies package.json files to remove private flags and generates random package names, leading to pollution of the npm registry.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.

You should uninstall the package immediately using 'npm uninstall suspicious_badger_cyan-58' and check for any dependencies that may be affected.

Currently, there are no specific patches available for the suspicious_badger_cyan-58 package, so the best course of action is to remove it.

Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities, helping you maintain the security of your software.

How To Fix

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

npm uninstall suspicious_badger_cyan-58

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