Malicious Code Injection in prospective_toucan_replicate_automation Package
Summary
MAL-2025-107369: Malicious code in prospective_toucan_replicate_automation (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The prospective_toucan_replicate_automation package is part of the npm ecosystem, typically used for automating tasks related to the Toucan project. It is designed to facilitate various automation processes but has been compromised by malicious actors. This vulnerability allows for the manipulation of package metadata, potentially affecting developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded in the prospective_toucan_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 automatic publication of derivative packages. This behavior can inflate developer reputation scores fraudulently and pollute the npm registry with numerous unwanted packages, posing a risk to other developers and users relying on the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall prospective_toucan_replicate_automationIf 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 affected package from your project by executing: npm uninstall prospective_toucan_replicate_automation. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The prospective_toucan_replicate_automation package has been compromised by malicious code that alters package metadata and publishes unwanted derivatives. It is crucial for developers to update or remove the package to maintain the integrity of their applications and the npm ecosystem.
See every vulnerability recorded for prospective_toucan_replicate_automation →
FAQ
The vulnerability involves malicious code that modifies package metadata and publishes unwanted packages to the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
The consequences include the inflation of developer reputation scores, pollution of the npm registry, and potential security risks for users relying on affected packages.
You should check the npm registry for a patched version of the prospective_toucan_replicate_automation package and update accordingly.
If an immediate update is not possible, consider uninstalling the package to mitigate risks until a secure version is available.
