Malicious Code Injection in AlexanderClark Package - npm Vulnerability
Summary
MAL-2025-170783: Malicious code in alexanderclark (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 AlexanderClark package is a Node.js module available on npm, primarily used for various functionalities in JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This specific vulnerability allows attackers to manipulate the package's metadata and publish harmful variants, posing a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability originates from the AlexanderClark package being associated with a malicious campaign that includes autopublish scripts. These scripts are designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, which can pollute the npm registry and inflate developer reputation scores fraudulently. The ramifications include potential exposure of projects to malicious code and a compromised npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alexanderclarkIf 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 AlexanderClark package from your project until a safe version is released. Use the following command to uninstall it: 'npm uninstall alexanderclark'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The AlexanderClark package has been identified as a vector for malicious code injection due to its association with a harmful npm campaign. Developers should take immediate action to mitigate risks by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for alexanderclark →
FAQ
The AlexanderClark package is a Node.js module used in JavaScript applications, but it has been compromised with malicious code.
This vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and functionality.
If you have installed the AlexanderClark package, it is recommended to uninstall it immediately and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup at Vulert Scanner.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
