Malicious Code Injection in elegant_lemur_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102039: Malicious code in elegant_lemur_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 elegant_lemur_replicate_automation package is part of the npm ecosystem, typically used for automation tasks. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry by publishing numerous variants with altered metadata.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious token reward campaign that floods the npm registry with fake 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 pollution of the npm registry and potential misuse of the affected packages. This can compromise the integrity of projects relying on these packages and may expose developers to security risks.

How To Fix

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

npm uninstall elegant_lemur_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 workaround, you can temporarily avoid using the elegant_lemur_replicate_automation package by removing it from your dependencies. You can do this by executing the command: npm uninstall elegant_lemur_replicate_automation. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The elegant_lemur_replicate_automation package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is crucial to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your project effectively.

See every vulnerability recorded for elegant_lemur_replicate_automation →

Share this vulnerability

FAQ

It is an npm package used for automation tasks but has been identified as part of a malicious campaign.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project if you rely on affected packages.

Currently, there is no specific patch for the elegant_lemur_replicate_automation package. It is advised to remove the package from your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

If you have used the elegant_lemur_replicate_automation package, it is recommended to uninstall it and review your project's dependencies for any other potentially malicious packages.

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 elegant_lemur_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