@s4yhiitestpoc/r3-https

On npm install, postinstall.js automatically collects host identity (hostname, username, uid/gid, homedir, platform, release), enumerates network interfaces (addresses, MACs, CIDRs), reads DNS servers and internal reverse-DNS names, captures npm/CI environment markers and container/runtime indicators, and walks up to eight parent directories to locate the consuming project's package.json and extract its name, version, declaring dependency field, and declared version range. The collected data is POSTed over HTTPS to the hardcoded endpoint collector.oob.s4yhii.com at path /_npm-poc/beacon, and a parallel DNS lookup to a labeled subdomain under *.oob.s4yhii.com is issued as an out-of-band beacon. The consumer manifest harvesting discloses the installer's private project identity and internal package naming to a third-party host and is the characteristic reconnaissance signal of a dependency-confusion targeting pipeline. The endpoint is not caller-configurable and there is no opt-out. ## Source: ghsa-malware (ff183ad61b543f94eaae7b4408fed43c924470b6a672090d0500b4836ff36bba) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.