Malicious Code Injection in envious_anaconda_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102138: Malicious code in envious_anaconda_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 envious_anaconda_replicate_automation package is part of the npm ecosystem, primarily used for automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish variants of itself with altered names and metadata.

Vulnerability Detail

The vulnerability originates from the package's involvement in a token reward campaign that exploits npm's publishing system. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of applications relying on this package, potentially introducing malicious code into production environments.

How To Fix

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

npm uninstall envious_anaconda_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 manually audit your package.json file and remove any references to envious_anaconda_replicate_automation. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.

Conclusion

The envious_anaconda_replicate_automation package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is crucial to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for envious_anaconda_replicate_automation →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.

You should uninstall the envious_anaconda_replicate_automation package immediately and audit your project for any other potentially malicious packages.

Yes, regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

You can find detailed information on the vulnerability from the source report or by using vulnerability monitoring tools like Vulert.

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