Malicious Code Vulnerability in @s4yhiitestpoc/r3-https Package
Summary
MAL-2026-17765: Malicious code in @s4yhiitestpoc/r3-https (npm). Affects @s4yhiitestpoc/r3-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/r3-https package is an npm module designed for handling HTTPS requests. It is intended to simplify secure communication in JavaScript applications. However, this package has been identified to contain malicious code that compromises user privacy and security by collecting sensitive information without consent.
Vulnerability Detail
The vulnerability originates from the postinstall.js script within the package, which executes automatically during the npm install process. This script collects sensitive host identity information, enumerates network interfaces, reads DNS servers, and captures environment markers. The collected data is then sent to a hardcoded external endpoint, exposing the user's project identity and internal package naming to potential attackers. This behavior is characteristic of a dependency-confusion attack, which can lead to further exploitation of the user's environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @s4yhiitestpoc/r3-httpsIf 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 prevent the execution of the postinstall script by using the following command when installing packages: npm install --ignore-scripts. However, this may affect the functionality of other packages that rely on postinstall scripts.
Conclusion
The @s4yhiitestpoc/r3-https package contains a serious vulnerability due to malicious code that collects sensitive information. Users are advised to update or remove the package and utilize tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for @s4yhiitestpoc/r3-https →
FAQ
The malicious code collects sensitive information from the user's environment and sends it to an external server without consent.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you cannot update the package, consider removing it from your project and looking for alternative packages that provide similar functionality without the security risks.
To prevent similar vulnerabilities, always review the code of third-party packages and use tools like Vulert to monitor for vulnerabilities in your dependencies.
The consequences include exposure of sensitive project information, potential unauthorized access to your environment, and increased risk of further attacks.
