Malicious Code Vulnerability in sensitive_damselfly_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108543: Malicious code in sensitive_damselfly_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The sensitive_damselfly_replicate_automation package is part of the npm ecosystem, often utilized for automation tasks. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. Its functionality has been compromised, making it a vector for malicious activities.

Vulnerability Detail

The vulnerability originates from the package being associated with a token reward campaign that floods npm with malicious packages. It contains scripts designed to automatically modify package.json files, removing private flags, changing version numbers, and generating random package names. This leads to pollution of the npm registry and potential security risks for developers who inadvertently use these packages.

How To Fix

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

npm uninstall sensitive_damselfly_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 manually remove the package from your project by executing: npm uninstall sensitive_damselfly_replicate_automation. Additionally, ensure that your package.json does not include any references to this package.

Conclusion

The sensitive_damselfly_replicate_automation package poses a significant risk due to its malicious code designed to manipulate npm registry entries. It is essential to take immediate action to remove this package and safeguard your projects from potential exploitation.

See every vulnerability recorded for sensitive_damselfly_replicate_automation →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative 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 uninstall the package immediately and check for any other dependencies that may be affected.

While specific exploits are not detailed, the modification of package.json can lead to unauthorized access and manipulation of your project.

Regularly audit your dependencies, use tools like Vulert for monitoring, and avoid installing packages from untrusted sources.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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