Which versions of @s4yhiitestpoc/r2-https are malicious?

The following npm versions of @s4yhiitestpoc/r2-https are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @s4yhiitestpoc/r2-https if I installed it?

@s4yhiitestpoc/r2-https is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @s4yhiitestpoc/r2-https — how do I know if it already compromised me?

If @s4yhiitestpoc/r2-https was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @s4yhiitestpoc/r2-https part of a known attack campaign?

Yes — @s4yhiitestpoc/r2-https is associated with the IN-MAL-2026-021432 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @s4yhiitestpoc/r2-https across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @s4yhiitestpoc/r2-https (version 1.0.0).

Malicious package

@s4yhiitestpoc/r2-httpsnpm

Advisory published Oct 11, 2026Updated Oct 11, 2026

@s4yhiitestpoc/r2-https is a confirmed malicious npm package (MAL-2026-17764) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @s4yhiitestpoc/r2-https (npm)

MAL-2026-17764

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @s4yhiitestpoc/r2-https

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b6042f718b39be380eeda7c31dc46b056e753cb8a39e51897c8106e49b44f4d0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @s4yhiitestpoc/r2-https (version 1.0.0).
If you installed it — respond
@s4yhiitestpoc/r2-https is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @s4yhiitestpoc/r2-https was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @s4yhiitestpoc/r2-https on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021432

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @s4yhiitestpoc/r2-https-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database