Malicious Code Injection in quarrelsome_turtle_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96144: Malicious code in quarrelsome_turtle_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 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 quarrelsome_turtle_requirement package is part of the npm ecosystem, often utilized for various JavaScript applications. It is designed to facilitate certain functionalities within projects but has been compromised. This package is linked to the tea.xyz token reward campaign, which has been associated with malicious activities aimed at inflating developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability stems from malicious code embedded in the quarrelsome_turtle_requirement package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a continuous republishing of these variants, which pollutes the npm registry and can lead to significant security risks, including unauthorized access and manipulation of project dependencies.

How To Fix

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

npm uninstall quarrelsome_turtle_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 quarrelsome_turtle_requirement package from your project until a secure version is released. You can do this by executing the following command: npm uninstall quarrelsome_turtle_requirement.

Conclusion

The quarrelsome_turtle_requirement package has been identified as containing malicious code that poses significant risks to projects using it. It is essential to take immediate action by updating or uninstalling the package to safeguard your applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for quarrelsome_turtle_requirement →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been compromised with malicious code.

The malicious code modifies your package.json, potentially leading to unauthorized package republishing and security vulnerabilities.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

As a temporary measure, you can uninstall the quarrelsome_turtle_requirement package to mitigate risks until a secure version is available.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest secure versions.

How To Fix

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

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