Malicious Code Vulnerability in @s4yhiitestpoc/r2-https Package
Summary
MAL-2026-17764: Malicious code in @s4yhiitestpoc/r2-https (npm). Affects @s4yhiitestpoc/r2-https versions 1.0.0. 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 @s4yhiitestpoc/r2-https package is an npm module designed for handling HTTPS requests. It is often utilized in Node.js applications for secure communication. However, this package has been found to contain malicious code that compromises user data and system integrity during installation.
Vulnerability Detail
The vulnerability arises from a postinstall script within the package that collects sensitive information from the user's environment, including hostname, username, and npm configuration values. This data is then sent to a third-party server without user consent. The malicious behavior is triggered automatically upon installation, posing significant risks to users, especially those using private npm registries.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @s4yhiitestpoc/r2-https
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
As a temporary measure, you can avoid using the package altogether and seek alternative libraries that provide similar functionality without the associated risks. Additionally, consider using npm audit to regularly check for vulnerabilities in your dependencies.
Conclusion
The @s4yhiitestpoc/r2-https package contains a serious vulnerability that collects and exfiltrates sensitive user data. It is essential for developers to uninstall this package immediately and monitor their applications for any potential security issues. Utilizing tools like Vulert can help maintain a secure development environment.
See every vulnerability recorded for @s4yhiitestpoc/r2-https →
FAQ
The malicious code collects sensitive information from the user's system and sends it to a third-party server without consent.
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.
Immediately uninstall the package using npm uninstall @s4yhiitestpoc/r2-https and check for any data breaches or security issues.
While specific exploits have not been detailed, the data exfiltration poses significant risks, especially for users with private npm registries.
Regularly audit your dependencies using npm audit, avoid installing unverified packages, and consider using tools like Vulert for real-time monitoring.