Malicious Code Vulnerability in bottom_lynx-gooddev Package

bottom_lynx-gooddev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100063: Malicious code in bottom_lynx-gooddev (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The bottom_lynx-gooddev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the npm registry, is intended to facilitate the development and deployment of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry for token rewards, leading to significant security risks.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the bottom_lynx-gooddev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which are then republished to the npm registry. The intent behind this is to inflate developer reputation scores for the tea protocol token rewards. The ramifications include potential exposure of sensitive data, pollution of the npm registry, and the risk of other developers inadvertently using compromised packages.

How To Fix

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

npm uninstall bottom_lynx-gooddev

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

Conclusion

The bottom_lynx-gooddev package contains a serious vulnerability that can compromise the integrity of applications using it. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for bottom_lynx-gooddev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities using just package-lock.json. Visit Vulert Scanner to check if your application is affected.

Using this package can lead to exposure of sensitive data, pollution of the npm registry, and potential exploitation of your application.

Check the npm registry for any updates to the bottom_lynx-gooddev package that may address this vulnerability.

Consider uninstalling the package as a temporary measure to mitigate the risk until a secure version is available.

How To Fix

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

npm uninstall bottom_lynx-gooddev

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