Malicious Code Injection in quaint_canid_z3n: A Threat to npm Packages

quaint_canid_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96128: Malicious code in quaint_canid_z3n (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

quaint_canid_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package, like others involved in the tea.xyz token reward scheme, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and metadata. Its primary function is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in quaint_canid_z3n stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, effectively polluting the npm registry. Originating from a campaign aimed at exploiting npm for token rewards, this vulnerability can result in developers unintentionally using compromised packages, leading to potential security risks and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall quaint_canid_z3n

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 quaint_canid_z3n package and any other packages that may be part of the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The quaint_canid_z3n package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for quaint_canid_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the introduction of compromised packages into your project, potentially exposing it to security risks.

You should uninstall the package immediately using the command npm uninstall quaint_canid_z3n.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall quaint_canid_z3n

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