Malicious Code Injection in grieving_turkey_requirement Package

grieving_turkey_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94754: Malicious code in grieving_turkey_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The grieving_turkey_requirement package is part of the npm ecosystem, typically utilized for various JavaScript applications. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This package has been identified as part of a scheme that generates and publishes derivative packages to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability in the grieving_turkey_requirement package stems from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall grieving_turkey_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 grieving_turkey_requirement package from your project by executing the command: 'npm uninstall grieving_turkey_requirement'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The grieving_turkey_requirement package has been identified as containing malicious code that can compromise applications. It is crucial to update or remove this package to maintain the security and integrity of your software. Utilizing tools like Vulert can help in monitoring and alerting for such vulnerabilities in real-time.

See every vulnerability recorded for grieving_turkey_requirement →

Share this vulnerability

FAQ

It is an npm package often involved in token reward campaigns, which can lead to the creation of malicious derivatives.

The vulnerability can lead to the injection of malicious code, altering your application's behavior and potentially compromising security.

You should update the package to the latest version or remove it entirely until a secure version is released.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without signing up.

How To Fix

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

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