Malicious Code Injection in abdushakur Package: A Threat to npm Users
Summary
MAL-2025-170636: Malicious code in abdushakur (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 abdushakur package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages with randomized names. This behavior poses significant risks to the integrity of the npm registry and the security of applications relying on this package.
Vulnerability Detail
The abdushakur package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This is part of a broader scheme associated with the tea.xyz token reward campaign, which floods the npm registry with derivative packages. The implications of this vulnerability include the potential for developers to unknowingly publish compromised packages, leading to reputational damage and security risks for applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall abdushakurIf 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 measure, avoid using the abdushakur package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your project's dependencies to ensure they are secure.
Conclusion
The abdushakur package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to take immediate action by removing this package and monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for abdushakur →
FAQ
The abdushakur package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the publication of compromised packages, which may introduce security risks and affect the integrity of your application.
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 by this vulnerability.
Uninstall the abdushakur package immediately using npm uninstall abdushakur and audit your dependencies for any other vulnerabilities.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.
