Critical Malicious Code Vulnerability in upload-to-play-store Package
Summary
MAL-2025-190939: Malicious code in upload-to-play-store (npm). Affects upload-to-play-store versions 1.0.1 – 1.0.2. 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 upload-to-play-store package is an npm library designed to facilitate the process of uploading applications to the Google Play Store. It simplifies the deployment process for developers, allowing them to automate uploads and manage app versions efficiently. However, this package has been identified to contain malicious code, posing significant security risks to any system using it.
Vulnerability Detail
The vulnerability originates from the upload-to-play-store package, specifically versions 1.0.1 and 1.0.2. It has been classified as containing embedded malicious code, which can compromise the entire system where the package is installed. This malicious code can lead to unauthorized access to sensitive information, including secrets and keys stored on the affected machine. As a result, any system running this package should be considered fully compromised, and immediate action is required to mitigate potential damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall upload-to-play-store
If 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
There are no effective workarounds to mitigate the risks posed by this malicious package. The only recommended action is to remove the package entirely from your system.
Conclusion
The upload-to-play-store package has been identified as containing malicious code, posing a severe risk to any systems using it. Immediate removal of the package and rotation of sensitive information is essential to mitigate potential damage. Utilizing tools like Vulert can help monitor and prevent future vulnerabilities.
See every vulnerability recorded for upload-to-play-store →
FAQ
You should remove the package immediately and rotate any sensitive information stored on your system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.
As of now, there is no patched version available. The best course of action is to remove the package entirely.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.