Malicious Code Injection in buyungupik: A Threat to npm Ecosystem
Summary
MAL-2025-170994: Malicious code in buyungupik (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 'buyungupik' 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that generate and publish numerous variants of the original package, potentially leading to security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the 'buyungupik' package originates from its association with the tea.xyz token reward campaign. The malicious code within this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which can pollute the npm registry and compromise the integrity of the ecosystem. The ramifications include increased exposure to malicious packages and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall buyungupikIf 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 'buyungupik' package from your project if it is not essential. Use the following command to uninstall it: 'npm uninstall buyungupik'. Additionally, consider using alternative packages that do not have known vulnerabilities.
Conclusion
The 'buyungupik' package poses a significant security risk due to its malicious code that exploits the npm registry. It is essential for developers to be vigilant and take immediate action to remove or update this package to protect their applications from potential threats. Utilizing tools like Vulert can aid in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for buyungupik →
FAQ
'buyungupik' is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
If you have installed 'buyungupik', it is recommended to uninstall it immediately and monitor for any updates or patches.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
