Malicious Code Injection in splendid_crane_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109020: Malicious code in splendid_crane_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 splendid_crane_replicate_automation package is part of the npm ecosystem, often utilized for automation tasks in JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, aimed at inflating developer reputation scores for token rewards. This package is particularly vulnerable due to its design, which allows for the automatic generation and publication of malicious variants.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the splendid_crane_replicate_automation package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and the undermining of trust in the npm ecosystem.

How To Fix

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

npm uninstall splendid_crane_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 splendid_crane_replicate_automation package from your project by executing 'npm uninstall splendid_crane_replicate_automation'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The splendid_crane_replicate_automation package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial for developers to stay vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for splendid_crane_replicate_automation →

Share this vulnerability

FAQ

It is an npm package used for automation tasks, but it has been compromised with malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

You should uninstall the package immediately and check for any updates or patches that may be available.

Using compromised packages can lead to security vulnerabilities, data breaches, and loss of trust in your software.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

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