Malicious Code Injection in monetary_cardinal_replicate_automation Package
Summary
MAL-2025-105948: Malicious code in monetary_cardinal_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 monetary_cardinal_replicate_automation package is part of the npm ecosystem, designed for automating tasks related to monetary data processing. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages are engineered to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
This vulnerability originates from a malicious payload embedded within the monetary_cardinal_replicate_automation package. The payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in compromised developer environments, loss of control over package integrity, and potential exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall monetary_cardinal_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 prevent the installation of this package by using npm's package-lock.json file to lock your dependencies. This will help avoid inadvertently installing the malicious package until a secure version is available.
Conclusion
The monetary_cardinal_replicate_automation package has been identified as a vector for malicious code that compromises the integrity of npm projects. It is crucial for developers to take immediate action to remove this package and implement best practices for dependency management to safeguard their applications.
See every vulnerability recorded for monetary_cardinal_replicate_automation →
FAQ
It is an npm package designed for automating monetary data processing tasks but has been compromised with malicious code.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities 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.
You should uninstall the package immediately using 'npm uninstall monetary_cardinal_replicate_automation' and review your dependencies for any potential risks.
Regularly update your packages, monitor your dependencies using tools like Vulert, and review the security advisories for the packages you use.
