Malicious Code Exploit in Beautiful Canid Z3N Package

beautiful_canid_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93361: Malicious code in beautiful_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 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

Beautiful Canid Z3N is an npm package that is part of a broader token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate certain functionalities within the ecosystem, but it has been compromised, leading to significant security concerns. The malicious nature of this package stems from its ability to generate and publish derivative packages with altered metadata, which can mislead developers and inflate reputation scores within the npm registry.

Vulnerability Detail

The vulnerability in the Beautiful Canid Z3N package originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches 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 beautiful_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 Beautiful Canid Z3N package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The Beautiful Canid Z3N package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for beautiful_canid_z3n →

Share this vulnerability

FAQ

Beautiful Canid Z3N is an npm package that was part of a token reward campaign, but it has been identified as malicious due to its ability to generate and publish compromised packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

You should uninstall the Beautiful Canid Z3N package immediately and look for secure alternatives to avoid security risks.

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 signing up.

How To Fix

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

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