Malicious Code Injection in suitable_cod-tool: npm Package Vulnerability

suitable_cod-tool Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109281: Malicious code in suitable_cod-tool (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The suitable_cod-tool is an npm package that has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and publish harmful variants to the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the suitable_cod-tool package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The result is a continuous republishing of these variants, which pollutes the npm registry and can lead to significant security risks for developers relying on these packages. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards, making it imperative for users to be vigilant.

How To Fix

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

npm uninstall suitable_cod-tool

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 remove the suitable_cod-tool package from your project by executing the command: npm uninstall suitable_cod-tool. This will prevent any malicious code from executing while you assess your options for a secure alternative.

Conclusion

The suitable_cod-tool package has been identified as a malicious entity within the npm ecosystem, capable of compromising project integrity through automated malicious activities. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for suitable_cod-tool →

Share this vulnerability

FAQ

The suitable_cod-tool package is an npm package involved in a malicious campaign that automates the creation and publication of derivative packages for token rewards.

The malicious code modifies your package.json file, removes private flags, and continuously republishes harmful variants, potentially compromising your project's integrity.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider uninstalling the package as a temporary measure to prevent any malicious activity.

You can find detailed information about npm package vulnerabilities on platforms like Vulert, which provides real-time alerts for open-source vulnerabilities.

How To Fix

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

npm uninstall suitable_cod-tool

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