Malicious Code Vulnerability in polymedr-minadadus-buie Package
Summary
MAL-2025-164412: Malicious code in polymedr-minadadus-buie (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 polymedr-minadadus-buie package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, its functionality has been compromised, leading to significant security risks.
Vulnerability Detail
The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of control over package management and potential exploitation of the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall polymedr-minadadus-buieIf 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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project.
Conclusion
The polymedr-minadadus-buie package contains malicious code that poses significant risks to users and their applications. It is essential to remove this package and monitor your dependencies to maintain security. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for polymedr-minadadus-buie →
FAQ
The malicious code modifies the package.json file, removes private flags, and generates random package names, leading to pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected.
While there are no specific workarounds, it is crucial to monitor your application for any unusual behavior and plan to remove the package as soon as possible.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Detailed information can be found in the vulnerability report from Amazon Inspector and on platforms like Vulert.
