Malicious Code Injection in disappointed_dolphin_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101611: Malicious code in disappointed_dolphin_replicate_automation (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 'disappointed_dolphin_replicate_automation' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to automate tasks related to package publishing. However, it has been compromised, leading to significant security concerns due to its malicious behavior.

Vulnerability Detail

This vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to reputation inflation for developers and pollution of the npm registry. The continuous republishing of these variants poses a risk to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall disappointed_dolphin_replicate_automation

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 'disappointed_dolphin_replicate_automation' package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'disappointed_dolphin_replicate_automation' package has been identified as containing malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor for any updates or alternatives to ensure the security of your projects.

See every vulnerability recorded for disappointed_dolphin_replicate_automation →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and floods the npm registry with compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

You should remove the package immediately and check for any alternative solutions that do not pose security risks.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

Using this package can lead to security breaches, reputation damage, and potential data loss due to the malicious behavior embedded within.

How To Fix

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

npm uninstall disappointed_dolphin_replicate_automation

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