Malicious Code Injection in hilarious_dolphin_beige-91: A Threat to npm Ecosystem

hilarious_dolphin_beige-91 Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103715: Malicious code in hilarious_dolphin_beige-91 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package hilarious_dolphin_beige-91 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. Its primary functionality is to serve as a token reward mechanism, but it has been compromised to include malicious scripts that can harm developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in hilarious_dolphin_beige-91 originates from its association with a malicious campaign that employs scripts to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to reputation damage for developers and misuse of the npm ecosystem.

How To Fix

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

npm uninstall hilarious_dolphin_beige-91

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 hilarious_dolphin_beige-91 and any packages that depend on it. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The hilarious_dolphin_beige-91 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package configurations and repopulates the registry with harmful variants. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for hilarious_dolphin_beige-91 →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, associated with a token reward campaign that floods the npm registry.

The vulnerability can lead to the pollution of the npm registry, potentially harming your project's integrity and reputation.

You should uninstall the package immediately using 'npm uninstall hilarious_dolphin_beige-91' and audit your dependencies.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall hilarious_dolphin_beige-91

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