@expo-probe-ff8e2b/snack-probe-c2a16: malicious npm package executes mutable GitHub branch payload on install
Severity: critical · Patch status: no-fix-needed · Since 2026-11-20
GitHub Advisory GHSA-v33p-qh9f-g4rp reports malicious npm package @expo-probe-ff8e2b/snack-probe-c2a16 versions 1.0.0 and 1.0.1. Its package.json depends on expo-prepare-probe-c2a16db2 via a mutable git branch ref, git+https://github.com/lordseidon/recon-vps.gitexpo-probe-1106-c2a16db2, rather than a pinned registry version or commit SHA. npm install clones whatever that branch points to and runs its lifecycle scripts without integrity checking. The package's own index.js is a one-line stub, so the install-time git dependency is the payload. The randomized scope/name and recon-vps repository suggest a reconnaissance-style supply-chain drop vehicle. No patched versions are listed; affected users should remove the package and audit installs. No in-the-wild exploitation is stated.
What to do
- Immediately remove @expo-probe-ff8e2b/snack-probe-c2a16 1.0.0/1.0.1 from projects and lockfiles; block the package and lordseidon/recon-vps in registry/proxy allowlists.
- If installed, treat the host as potentially compromised: inspect npm lifecycle logs, review processes and network connections, and rotate credentials/secrets accessible to the install user.
- Audit package.json and lockfiles for git+https dependencies with mutable branch refs; pin to commit SHAs or registry versions with integrity hashes.
- Run npm install with ignore-scripts where feasible and use a sandboxed CI runner for untrusted dependencies.
- Search CI logs and artifact caches for the package name and dependency; rebuild from clean environments.
Sources
All live incidents on Threat Watch