Malicious Code Injection in compulsory_canidae-tool: A Threat to npm Packages

compulsory_canidae-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100797: Malicious code in compulsory_canidae-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 compulsory_canidae-tool is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to manipulate its own metadata and publish derivative versions to inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious scripts within the compulsory_canidae-tool package. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing system for malicious purposes.

How To Fix

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

npm uninstall compulsory_canidae-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 measure, avoid using the compulsory_canidae-tool package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your npm packages to identify and remove any that may be compromised.

Conclusion

The compulsory_canidae-tool package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for compulsory_canidae-tool →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The malicious code can alter your package metadata, leading to potential security risks and the pollution of the npm registry.

You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Uninstall the compulsory_canidae-tool package immediately and audit your dependencies for any other potential vulnerabilities.

Yes, look for other npm packages that provide similar functionality but are known to be secure and trustworthy.

How To Fix

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

npm uninstall compulsory_canidae-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