Malicious Code Vulnerability in lobster-notthedevs Package
Summary
MAL-2025-105292: Malicious code in lobster-notthedevs (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The lobster-notthedevs package is part of the npm ecosystem, typically used for various development purposes. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages with altered metadata, which can lead to significant issues within the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the lobster-notthedevs package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to the pollution of the npm registry. The autopublish scripts included in the package are designed to continuously republish these variants, potentially compromising the integrity of the npm ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lobster-notthedevsIf 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 prevent the installation of the lobster-notthedevs package by using npm's package-lock.json file to lock dependencies. Additionally, you can monitor your project for vulnerabilities using Vulert, which analyzes your package-lock.json for any open-source vulnerabilities in real-time.
Conclusion
The lobster-notthedevs package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and stay informed about potential vulnerabilities using tools like Vulert.
See every vulnerability recorded for lobster-notthedevs →
FAQ
lobster-notthedevs is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting other developers.
You should immediately remove the lobster-notthedevs package from your project and monitor for any updates or patches.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file, providing real-time insights into potential risks.
