Malicious code in ecto-win-flag-q2m7 (npm)

---

__

Source: amazon-inspector (a6344042aff547b32cf30bc456be25e1229f921217ec0d6777f470174df10792)

On npm install, postinstall.js executes a harvest-and-exfiltrate chain against the installer's machine. It reads files under /app, /root, and /flag.txt, shells out via execFileSync('/bin/sh', ['-c',...]) to recursively grep the filesystem for HTB{...} flag patterns and collect git history, gathers host identifiers (uid, cwd, hostname), and transmits the collected data via HTTP PUT to a hardcoded attacker endpoint at http://154.57.164.82:31250/api/modules/ECT-*. The script includes sandbox-evasion gating that exits cleanly when cwd contains /tmp/npm-safe or /tmp/pkg, or when hostname matches nijin, hetzner, or ec2.internal — ensuring the malicious path only fires on real installer machines. The combination of unconditional filesystem read, hardcoded non-registry IP destination, and scanner-evasion logic is an unambiguous supply-chain attack.

Source: ghsa-malware (572f6a0b3a14892c3b86a30ede324f314a1f933c49e8376090756050a8e7a891)

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.