@expo-probe-ff8e2b/snack-probe-c2a16@1.0.1
Malicious code in @expo-probe-ff8e2b/snack-probe-c2a16 (npm)
Analysis
@expo-probe-ff8e2b/snack-probe-c2a16@1.0.1 is an inert stub — index.js is `module.exports = 1;`, there are no lifecycle scripts and no executable code in the tarball. Its only function is to pull in a dependency from a non-registry source: "expo-prepare-probe-c2a16db2": "git+hxxps://github[.]com/lordseidon/recon-vps[.]git#expo-probe-1106-c2a16db2". Installing the package therefore makes the package manager clone and build that external GitHub repository at a mutable, per-run ref (date-coded 1106 plus the tag c2a16db2) on a repository named recon-vps, so any code published to that ref executes in the installer's environment without ever passing through a registry tarball. The registry artifact itself is only the trigger; no second-stage payload is contained in the published package. IOCs: github[.]com/lordseidon/recon-vps (ref expo-probe-1106-c2a16db2), dependency name expo-prepare-probe-c2a16db2.
- analyzed by
- Leitwacht
- first seen
- Nov 6, 2026, 02:35 PM
- analyzed
- Nov 6, 2026, 02:36 PM
Related advisories
- @expo-probe-ff8e2b/snack-probe-c2a16@1.0.0 same package
- @memtensor/memos-cloud-openclaw-plugin@0.1.22
- nullsub@1.11.16
- @yuanjielab/cli@0.9.0
- teick@1.0.2
- teick@1.0.1
- @denzz221/baileys@7.0.0
- quiche-tea-curut@4.3.4
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.