Malicious Code Injection in then_cattle_requirement Package

then_cattle_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96980: Malicious code in then_cattle_requirement (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'then_cattle_requirement' package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the integration of various libraries and tools within a project. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the generation of derivative packages.

Vulnerability Detail

The vulnerability in the 'then_cattle_requirement' package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file, removing private flags, altering version numbers, and creating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall then_cattle_requirement

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 'then_cattle_requirement' package until a fixed version is released. Additionally, you can monitor your package-lock.json file for any unauthorized changes and revert them if necessary.

Conclusion

The 'then_cattle_requirement' package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can further enhance your security posture by monitoring for vulnerabilities in real-time.

See every vulnerability recorded for then_cattle_requirement →

Share this vulnerability

FAQ

It is an npm package used for managing dependencies in JavaScript applications, but it has been compromised by malicious actors.

If you have this package installed, your application may be at risk of incorporating malicious code that can compromise its security.

You should update the package to a patched version or remove it from your project to mitigate the risk.

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

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall then_cattle_requirement

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