Malicious Code Injection in gay_lamprey_requirement Package

gay_lamprey_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94654: Malicious code in gay_lamprey_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 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 gay_lamprey_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with altered metadata, which can lead to significant security risks for developers and their projects.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the gay_lamprey_requirement package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The malicious payload can compromise the integrity of projects that depend on this package, potentially allowing unauthorized access or manipulation of the codebase.

How To Fix

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

npm uninstall gay_lamprey_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 gay_lamprey_requirement package from your project by executing the command: 'npm uninstall gay_lamprey_requirement'. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The gay_lamprey_requirement package contains malicious code that poses a significant risk to developers and their projects. It is crucial to take immediate action by updating or removing the package to safeguard your application. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure your software remains secure.

See every vulnerability recorded for gay_lamprey_requirement →

Share this vulnerability

FAQ

The gay_lamprey_requirement package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to unauthorized changes in your project's dependencies, potentially compromising the security and integrity of your application.

If you have installed the gay_lamprey_requirement package, you should uninstall it immediately and check for any other affected packages.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing the package-lock.json file.

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

How To Fix

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

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