Malicious Code Injection in ltd_crow_z3n Package: A Threat to npm Ecosystem

ltd_crow_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105372: Malicious code in ltd_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 ltd_crow_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the ltd_crow_z3n package stems from its inclusion in a malicious campaign that deploys autopublish scripts. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry with numerous unwanted packages, which can compromise the integrity of the ecosystem and potentially expose users to further security risks.

How To Fix

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

npm uninstall ltd_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 ltd_crow_z3n package in your projects. Additionally, consider using the following command to uninstall the package if it is already installed: npm uninstall ltd_crow_z3n.

Conclusion

The ltd_crow_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the registry. It is essential for developers to be vigilant and take immediate action to remove this package and monitor their applications for vulnerabilities.

See every vulnerability recorded for ltd_crow_z3n →

Share this vulnerability

FAQ

The ltd_crow_z3n package is an npm package that has been linked to a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to the pollution of the npm registry, potentially exposing your application to malicious packages and compromising its security.

You should uninstall the ltd_crow_z3n package immediately and monitor for any updates or patches that may address this issue.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.

Regularly audit your dependencies, keep them updated, and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.

How To Fix

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

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