Malicious Code Injection in big_puffin_dumbs Package: A Threat to npm Users

big_puffin_dumbs Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99970: Malicious code in big_puffin_dumbs (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The big_puffin_dumbs 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 known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts, leading to potential security risks for users.

Vulnerability Detail

The vulnerability in the big_puffin_dumbs package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The origin of this vulnerability is linked to a broader campaign aimed at exploiting the npm ecosystem for token rewards, which can lead to compromised systems and unintentional use of malicious packages by developers.

How To Fix

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

npm uninstall big_puffin_dumbs

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 big_puffin_dumbs package and monitor your dependencies for any similar malicious packages. Regularly audit your npm packages using 'npm audit' to identify vulnerabilities.

Conclusion

The big_puffin_dumbs package poses a significant threat to npm users due to its malicious code designed to manipulate package management. It is crucial to remove this package and monitor your dependencies to maintain the security of your projects. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities.

See every vulnerability recorded for big_puffin_dumbs →

Share this vulnerability

FAQ

The big_puffin_dumbs package is an npm package that has been identified as malicious, primarily used in a token reward campaign to manipulate developer reputation.

The malicious code modifies your package.json file, potentially leading to the inclusion of unwanted packages and compromising the integrity of your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

If you have installed the big_puffin_dumbs package, you should uninstall it immediately using 'npm uninstall big_puffin_dumbs' and audit your project for any other vulnerabilities.

Yes, be cautious of packages that appear to be part of the tea.xyz token reward campaign, as they may contain similar malicious code. Regularly audit your dependencies.

How To Fix

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

npm uninstall big_puffin_dumbs

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