@gfe/lx-watchernpm

All three npm lifecycle hooks (preinstall, install, postinstall) invoke install.js, which POSTs the installer's hostname, OS username, current working directory, timestamp, and hook name to a hardcoded webhook.site collector at https://webhook.site/df384ffa-1094-4bbf-a202-e8b345b3ed18/gfe. The exfiltration fires automatically on npm install with no caller consent and no configuration. The package's main is a no-op createWatcher stub, so a build that resolves this scoped name silently succeeds while host identifiers are leaked. The scoped @gfe/* name combined with the no-op stub and the install-time beacon is the canonical dependency-confusion shape: any organization whose private @gfe/lx-watcher resolves against the public registry leaks host, username, and install-path metadata to the author-controlled collector.

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.