Malicious Code Vulnerability in astroartisan: Exploitation of npm Registry
Summary
MAL-2025-170927: Malicious code in astroartisan (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
astroartisan is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm ecosystem. However, it has been compromised, leading to significant security concerns. The vulnerability allows malicious actors to manipulate the package's metadata and behavior, resulting in the proliferation of harmful derivatives in the npm registry.
Vulnerability Detail
The vulnerability in the astroartisan package originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry with potentially harmful packages, posing risks to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall astroartisanIf 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 astroartisan package from your project to prevent any potential exploitation. This can be done using the command: npm uninstall astroartisan. Additionally, consider using alternative packages that do not have known vulnerabilities.
Conclusion
The astroartisan package has been identified as having a serious vulnerability due to its involvement in a malicious npm campaign. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for astroartisan →
FAQ
The vulnerability involves malicious code that modifies package metadata and publishes harmful derivatives to the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
The risks include the potential for malicious code execution, pollution of the npm registry, and compromised developer reputation scores.
Check the npm registry for the latest version of the astroartisan package. If a patched version is available, updating the package will resolve the vulnerability.
If immediate updates are not possible, consider removing the package from your project as a temporary measure to mitigate risks.
