Malicious Code Exploit in famous_angelfish_dumbs Package: npm Vulnerability Overview

famous_angelfish_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102556: Malicious code in famous_angelfish_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 famous_angelfish_dumbs package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of this package, however, has been compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability in the famous_angelfish_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, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with numerous similar malicious packages. The ramifications include potential security risks for developers who inadvertently use these packages, as they may unknowingly contribute to the pollution of the npm ecosystem.

How To Fix

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

npm uninstall famous_angelfish_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, avoid using the famous_angelfish_dumbs package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.

Conclusion

The famous_angelfish_dumbs package presents a significant security 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 monitor their projects for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for famous_angelfish_dumbs →

Share this vulnerability

FAQ

The famous_angelfish_dumbs package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to your project being associated with malicious activities, potentially compromising its integrity and security.

If you have installed the famous_angelfish_dumbs package, you should uninstall it immediately and check your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.

Yes, consider using well-established and reputable packages that provide similar functionality without the risks associated with malicious packages.

How To Fix

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

npm uninstall famous_angelfish_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