Malicious Code Vulnerability in disturbed_dolphin_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101663: Malicious code in disturbed_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 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 disturbed_dolphin_replicate_automation package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate automation processes. However, this package has been identified as part of a malicious campaign that floods the npm registry with derivative packages, which can compromise the integrity of applications relying on it.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which employs malicious scripts to manipulate package metadata. These scripts remove private flags from package.json, alter version numbers, and generate numerous derivative packages with random names, ultimately polluting the npm registry. This can lead to security risks, including the potential for unauthorized access and misuse of application data.

How To Fix

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

npm uninstall disturbed_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 disturbed_dolphin_replicate_automation package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The disturbed_dolphin_replicate_automation package poses a significant security risk due to its malicious code. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.

See every vulnerability recorded for disturbed_dolphin_replicate_automation →

Share this vulnerability

FAQ

It is an npm package used for automation processes, but it has been compromised with malicious code.

The vulnerability can lead to unauthorized modifications in your package.json file and may expose your application to security risks.

You should uninstall the package immediately and look for alternatives to mitigate the risk.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

How To Fix

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

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