Malicious Code Injection in tall_owl_requirement Package

tall_owl_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96925: Malicious code in tall_owl_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tall_owl_requirement package is part of the npm ecosystem, designed to facilitate various functionalities within JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is particularly vulnerable due to its association with the tea.xyz token reward scheme, which incentivizes the creation of numerous low-quality packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the tall_owl_requirement package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to manipulate the npm registry by flooding it with numerous derivative packages. The ramifications include potential security risks for developers who inadvertently use these packages, as they can lead to reputation damage and compromised application integrity.

How To Fix

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

npm uninstall tall_owl_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 remove the tall_owl_requirement package from your project until a secure version is released. You can do this by executing the following command: npm uninstall tall_owl_requirement. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The tall_owl_requirement package has been identified as containing malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential vulnerabilities.

See every vulnerability recorded for tall_owl_requirement →

Share this vulnerability

FAQ

The tall_owl_requirement package is an npm package that has been identified as part of a malicious campaign to flood the npm registry with low-quality derivative packages.

The vulnerability can lead to security risks, including the potential for reputation damage and compromised application integrity due to the malicious code embedded in the package.

You should update the package to the latest version or remove it from your project until a secure version is available.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

More information can be found in the vulnerability details provided by sources like Amazon Inspector and the npm registry.

How To Fix

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

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