Malicious Code Injection in amjadsami41 Package - npm Vulnerability
Summary
MAL-2025-170871: Malicious code in amjadsami41 (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 amjadsami41 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to create and publish derivative packages with random names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The package's functionality is compromised, making it a potential threat to users and developers relying on its integrity.
Vulnerability Detail
The vulnerability originates from the amjadsami41 package being involved in a malicious campaign that modifies its package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on this package. The malicious payload can affect the integrity of the software supply chain, leading to unintended consequences for developers and users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall amjadsami41If 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 amjadsami41 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes using tools like Vulert.
Conclusion
The amjadsami41 package poses a significant risk due to its involvement in a malicious campaign that alters package metadata and republishing behavior. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for amjadsami41 →
FAQ
The amjadsami41 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can compromise the integrity of your application by introducing malicious code and potentially leading to security breaches.
You should uninstall the amjadsami41 package immediately using 'npm uninstall amjadsami41' and look for alternative packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
