Malicious Code Injection in charming_locust_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100346: Malicious code in charming_locust_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 charming_locust_replicate_automation package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is designed to facilitate automation tasks but has been compromised to include malicious code. The vulnerability stems from its association with a token reward campaign that exploits npm's publishing mechanisms, leading to potential abuse of developer reputation systems.

Vulnerability Detail

The vulnerability in the charming_locust_replicate_automation package is characterized by the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The origin of this vulnerability is linked to a campaign that aims to inflate developer reputation scores for token rewards, potentially leading to a polluted npm registry and undermining the integrity of the ecosystem.

How To Fix

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

npm uninstall charming_locust_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 remove the charming_locust_replicate_automation package from your project by executing the following command: 'npm uninstall charming_locust_replicate_automation'. This will prevent any malicious code from executing while you assess the situation.

Conclusion

The charming_locust_replicate_automation package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your projects from potential exploitation.

See every vulnerability recorded for charming_locust_replicate_automation →

Share this vulnerability

FAQ

It is an npm package designed for automation tasks but has been compromised to include malicious code.

The malicious code modifies your package.json, potentially leading to unauthorized republishing of your packages and pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Consider uninstalling the package as a temporary measure to mitigate the risk while you plan for a proper fix.

Detailed information can be found in the vulnerability report provided by Amazon Inspector and on the GitHub repository for malicious packages.

How To Fix

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

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