Which versions of @gfe/lx-watcher are malicious?

The following npm versions of @gfe/lx-watcher are flagged malicious: 1.5.3, 1.5.4. Treat any of these as compromised.

How do I remediate @gfe/lx-watcher if I installed it?

@gfe/lx-watcher is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @gfe/lx-watcher — how do I know if it already compromised me?

If @gfe/lx-watcher was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @gfe/lx-watcher part of a known attack campaign?

Yes — @gfe/lx-watcher is associated with the IN-MAL-2026-018507, IN-MAL-2026-018508 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @gfe/lx-watcher across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @gfe/lx-watcher (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @gfe/lx-watcher across your stack and pipelines.

Malicious package

@gfe/lx-watchernpm

@gfe/lx-watcher is a confirmed malicious npm package (MAL-2026-14353) that steals credentials and exfiltrates sensitive data (malicious versions 1.5.3, 1.5.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @gfe/lx-watcher (npm)

MAL-2026-14353

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @gfe/lx-watcher

What this malware does

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.

Malicious versions

2 flagged

1.5.31.5.4

Indicators of compromise (SHA-256)

1635894d4aed4d98b67666bfe1f849af2884d5c455203d122abe866154a1063b

22abe9bf1ccb266833585bda205a07bc5c9a728763a733aa48b08fe50b640b4e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @gfe/lx-watcher (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @gfe/lx-watcher across your stack and pipelines.
If you installed it — respond
@gfe/lx-watcher is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @gfe/lx-watcher was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @gfe/lx-watcher before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @gfe/lx-watcher on npm has been identified as a malicious package (versions 1.5.3, 1.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018507IN-MAL-2026-018508

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @gfe/lx-watcher-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database