Malicious Code Exploit in tremendous_buzzard-appteadev Package

tremendous_buzzard-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109818: Malicious code in tremendous_buzzard-appteadev (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 tremendous_buzzard-appteadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability originates from the tremendous_buzzard-appteadev package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify the package.json file, removing private flags and changing version numbers. This behavior allows the package to continuously republish variants under randomized names, thereby polluting the npm registry and potentially compromising the integrity of applications that depend on it. The ramifications include the risk of unintentional use of malicious code, which can lead to data breaches or unauthorized access to systems.

How To Fix

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

npm uninstall tremendous_buzzard-appteadev

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 avoid using the tremendous_buzzard-appteadev package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The tremendous_buzzard-appteadev package poses a significant security risk due to its association with a malicious npm campaign. It is essential for developers to be vigilant about the packages they use, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their applications from potential threats.

See every vulnerability recorded for tremendous_buzzard-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can help you determine if your application is affected.

Using compromised packages can lead to security vulnerabilities, including data breaches, unauthorized access, and the potential for malicious code execution within your application.

Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.

Immediately uninstall the tremendous_buzzard-appteadev package and replace it with a secure alternative. Review your code for any potential impacts from the malicious code.

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 tremendous_buzzard-appteadev

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