Malicious Code Injection in alexsophieharrisonanderclark Package: A Threat to npm Ecosystem
Summary
MAL-2025-170789: Malicious code in alexsophieharrisonanderclark (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 'alexsophieharrisonanderclark' package is part of a broader campaign targeting the npm ecosystem, specifically related to the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate npm's publishing system by generating and publishing numerous derivative packages with randomized names. The intent is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the 'alexsophieharrisonanderclark' package. This code 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 a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall alexsophieharrisonanderclarkIf 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 avoid using the 'alexsophieharrisonanderclark' package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.
Conclusion
The 'alexsophieharrisonanderclark' package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry with derivative packages. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert for ongoing monitoring.
See every vulnerability recorded for alexsophieharrisonanderclark →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your project to security risks if you inadvertently use affected packages.
You should remove the 'alexsophieharrisonanderclark' package from your project and monitor for any updates or patches.
Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities in real-time without requiring installation. You can use their playground to check your application.
Report any malicious packages to the npm registry and remove them from your project immediately.
