MAL-2026-17764 Malicious code in @s4yhiitestpoc/r2-https (npm)
Malicious package
Published
MAL-2026-17764 is a malicious package: @s4yhiitestpoc/r2-https (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17764/ (Markdown: https://insights.sbomify.com/MAL-2026-17764/index.md)
- Package
- @s4yhiitestpoc/r2-https
- Registry
- npm
What is MAL-2026-17764?
MAL-2026-17764 is a malicious package in @s4yhiitestpoc/r2-https, published on 11 Oct 2026.
Official description
On npm install, the package's declared postinstall script (postinstall.js) collects installer host fingerprint data — hostname, username, home directory, platform/arch/OS release, current working directory, install directory, DNS server list, non-internal network interface addresses, Node.js version, and npm_* environment values including npm_config_registry — and POSTs the collected JSON to https://collector.oob.s4yhii.com/_npm-poc/beacon. It additionally performs an out-of-band DNS lookup against a subdomain of oob.s4yhii.com (db03o8lag74hsugsg2j091t8mfcf437h3.oob.s4yhii.com) to confirm execution via DNS exfiltration. The destination is a hardcoded author-controlled domain, the behavior fires automatically at install time without consent, and the exfiltrated data includes npm_config_registry which can disclose an internal/private registry URL. A self-described 'PoC' or 'coordinated disclosure' framing does not change the fact that installer-identifying data and internal registry configuration leave the host to a third-party endpoint.
What should I do about MAL-2026-17764?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.