Malicious Code Injection in professional_crow_z3n: A Threat to npm Ecosystem

professional_crow_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107310: Malicious code in professional_crow_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

The package professional_crow_z3n is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability in professional_crow_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 variants, which pollutes the npm registry and can compromise the security of applications that inadvertently depend on these malicious packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.

How To Fix

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

npm uninstall professional_crow_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 measure, you can avoid using the professional_crow_z3n package and any other packages associated with the tea.xyz campaign. Regularly audit your package.json and package-lock.json files to identify and remove any suspicious packages.

Conclusion

The professional_crow_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies. By removing this package and utilizing tools like Vulert, developers can enhance the security of their applications.

See every vulnerability recorded for professional_crow_z3n →

Share this vulnerability

FAQ

professional_crow_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

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

You should uninstall the professional_crow_z3n package immediately and review your project for any other potentially harmful packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

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

How To Fix

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

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