Malicious Code Injection in technical_canid_z3n Package

technical_canid_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96937: Malicious code in technical_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

The technical_canid_z3n package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is associated with the tea.xyz token reward scheme, which incentivizes developers to publish numerous derivative packages, often leading to reputation inflation and registry pollution.

Vulnerability Detail

The vulnerability in the technical_canid_z3n package originates from its malicious code designed to manipulate the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of unwanted packages in the npm registry. This not only affects the integrity of the npm ecosystem but can also compromise the security of applications relying on these packages, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall technical_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 technical_canid_z3n package and replace its functionality with alternative packages that are known to be secure. Always review the dependencies in your package-lock.json file to ensure no malicious packages are present.

Conclusion

The technical_canid_z3n package poses a significant risk due to its malicious code that alters package metadata and proliferates unwanted packages in the npm registry. It is essential to remove this package and monitor your project for vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for technical_canid_z3n →

Share this vulnerability

FAQ

The technical_canid_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of numerous derivative packages.

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

You should uninstall the technical_canid_z3n package immediately and check for any other potentially malicious packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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