Malicious Code Injection in favourite_python_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102651: Malicious code in favourite_python_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The favourite_python_replicate_automation package is an npm module that is part of a broader ecosystem aimed at automating Python replication tasks. However, it has been compromised and is now associated with a malicious campaign that seeks to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability stems from the package being part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to flood the npm registry with numerous variants, thereby polluting the ecosystem and potentially leading to security risks for users who unknowingly install these compromised packages. The malicious code can lead to unauthorized access, data breaches, and a loss of trust in the npm registry.

How To Fix

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

npm uninstall favourite_python_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 measure, avoid using the favourite_python_replicate_automation package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The favourite_python_replicate_automation package has been identified as a vector for malicious code that can compromise your project. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for favourite_python_replicate_automation →

Share this vulnerability

FAQ

It is an npm module designed for automating Python replication tasks but has been compromised with malicious code.

The malicious code modifies your package.json, removes private flags, and floods the npm registry with unwanted packages, posing security risks.

You should uninstall the package immediately using npm uninstall favourite_python_replicate_automation.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code directly.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

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