This report shows the evidence for @expo-probe-ff8e2b/snack-probe-c2a16@1.0.1. 2 of 2 known versions are blocked or flagged.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20314 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20314 confirms this npm version as malicious.
Advisory
MAL-2026-20314
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @expo-probe-ff8e2b/snack-probe-c2a16 (npm)
Details
package.json declares a dependency `expo-prepare-probe-c2a16db2` whose source is `git+https://github.com/lordseidon/recon-vps.git#expo-probe-1106-c2a16db2` — a mutable git branch ref on an external repository rather than a pinned registry version. On `npm install`, npm clones that repository at whatever commit the branch currently points to and runs any lifecycle scripts it contains, with no version pin, no commit SHA, and no integrity check. The shipped `index.js` is a one-line stub (`module.exports = 1`), so the entire functional payload of installing this package is whatever the referenced branch resolves to at install time. Additional context: the referenced repository is named `recon-vps`, the package name is a randomized `snack-probe-c2a16` under a disposable `@expo-probe-ff8e2b` scope, and the dependency name mirrors a probe-shaped identifier — consistent with a reconnaissance-style supply-chain drop vehicle.
LPM's AI review found this version clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The visible entry point only exports a constant, and the manifest declares no lifecycle scripts. A GitHub-hosted dependency is listed, but the available package source provides no evidence that it performs harmful actions.
Static reason
One or more suspicious static signals were detected.
Trigger
Importing the package loads index.js.
Impact
No harmful impact is evident from the available source.
Mechanism
The entry point exports a constant and performs no visible actions. The manifest also specifies a GitHub-hosted dependency, whose source is not included in this snapshot.
Network endpoints1
github.com
Independent scan evidence
public snapshot
AI called this Clean at 82.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The package entry point only exports the number 1; it performs no visible work at import time.
The manifest declares no lifecycle scripts, bin, or other entry points.
Evidence against
The manifest includes a dependency fetched from a GitHub repository; that dependency's source is not present in this package snapshot.
Behavioral surface
SourceNo risky source behavior triggered.
Supply chainTrivial
ManifestGit dependency · No license
Scanned 1 file · 20 B of source
Findings
2 high · 1 medium · 1 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
This report applies to @expo-probe-ff8e2b/snack-probe-c2a16@1.0.1.
The versions list below shows the verdict for each recorded version.
Avoid installing @expo-probe-ff8e2b/snack-probe-c2a16@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.