Malicious Code Injection in automatic_cow_z3n: A Threat to npm Packages

automatic_cow_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93305: Malicious code in automatic_cow_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'automatic_cow_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of these packages is compromised by malicious scripts that alter package metadata and republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'automatic_cow_z3n' originates from its association with malicious autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate 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 also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall automatic_cow_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 workaround, you can prevent the installation of this package by using npm's package-lock.json to monitor your dependencies. If you are using Vulert, you can check for vulnerabilities in your application without any signup by visiting the Vulert playground at https://vulert.com/scanner.

Conclusion

The 'automatic_cow_z3n' package poses a significant threat due to its malicious code that alters package metadata and contributes to npm registry pollution. It is essential to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for automatic_cow_z3n →

Share this vulnerability

FAQ

The impact includes the potential for npm registry pollution and the risk of developers using compromised packages unknowingly.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without requiring any signup.

You should uninstall the package immediately and monitor your dependencies for any further vulnerabilities.

Currently, there is no known patched version of the automatic_cow_z3n package available.

Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

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