Malicious Code Exploit in bedgan-notthedevs Package: A Threat to npm Users

bedgan-notthedevs Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99883: Malicious code in bedgan-notthedevs (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 bedgan-notthedevs package is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for tea protocol token rewards. However, its functionality has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the bedgan-notthedevs package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants, thereby undermining the integrity of the ecosystem. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and degradation of the npm registry's reliability.

How To Fix

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

npm uninstall bedgan-notthedevs

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 bedgan-notthedevs package from your project by executing the following command: npm uninstall bedgan-notthedevs. This will prevent any malicious activity associated with the package until a fix is applied.

Conclusion

The bedgan-notthedevs package poses a significant security risk due to its malicious code that alters project files and pollutes the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for bedgan-notthedevs →

Share this vulnerability

FAQ

The bedgan-notthedevs package is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The vulnerability can lead to unauthorized modifications of your package.json file and potentially expose your application to further security risks.

You should immediately uninstall the package and check for any unauthorized changes in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall bedgan-notthedevs

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