Malicious Code Injection in aaravinayak Package: npm Vulnerability Overview
Summary
MAL-2025-170612: Malicious code in aaravinayak (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 aaravinayak package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages. The vulnerability stems from the package's ability to modify critical files, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the aaravinayak package involves malicious code that alters the package.json file by removing private flags and changing version numbers. This code also generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. The origin of this issue is tied to a broader campaign that exploits npm's publishing mechanisms, potentially leading to reputation damage for developers and pollution of the npm registry with untrustworthy packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall aaravinayakIf 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 the aaravinayak package by using npm's package-lock.json to monitor your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The aaravinayak package poses a significant security risk due to its malicious code that alters essential project files and publishes untrustworthy variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for aaravinayak →
FAQ
The aaravinayak package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the modification of your package.json file, potentially exposing your project to security risks and pollution of the npm registry.
You should uninstall the aaravinayak package immediately using 'npm uninstall aaravinayak' and monitor your project for any further vulnerabilities.
Yes, regularly monitor your dependencies using tools like Vulert and ensure to review and audit packages before installation.
You can find detailed information about this vulnerability in the Open Source Vulnerability database and by using monitoring tools like Vulert.
