Malicious Code Injection in endless_lobster_z3n Package: A Threat to npm Ecosystem

endless_lobster_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102093: Malicious code in endless_lobster_z3n (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 endless_lobster_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality has been compromised, making it a vector for malicious code that can affect developers and users alike.

Vulnerability Detail

The vulnerability in the endless_lobster_z3n package originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers' reputations and the integrity of the npm ecosystem.

How To Fix

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

npm uninstall endless_lobster_z3n

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 endless_lobster_z3n package from your project by executing the command: 'npm uninstall endless_lobster_z3n'. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The endless_lobster_z3n package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and inflates developer reputation scores. It is essential to take immediate action by updating or removing the package to safeguard your projects and maintain the integrity of the npm registry.

See every vulnerability recorded for endless_lobster_z3n →

Share this vulnerability

FAQ

endless_lobster_z3n is an npm package that has been linked to malicious activities aimed at manipulating developer reputation scores within the npm ecosystem.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and reputation.

If you have installed the endless_lobster_z3n package, it is crucial to uninstall it immediately and check for any updates or patches from the package repository.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only the package-lock.json file to provide alerts.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign 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 endless_lobster_z3n

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