NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@expo-probe-ff8e2b/snack-probe-c2a16npm

Advisory published Updated

@expo-probe-ff8e2b/snack-probe-c2a16 is a confirmed malicious npm package (MAL-2026-20314) that opens a backdoor for remote access (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-20314
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @expo-probe-ff8e2b/snack-probe-c2a16

What this malware does

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.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

d4d78b492a057271ec603f4097e29baad85f90b811a0ade4e05daf704b26a41a
fb7d122bc958c315517274fe03a2bae44dd4a62e80daf29c102ef861c853371e

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @expo-probe-ff8e2b/snack-probe-c2a16 (2 malicious versions).

  2. If you installed it — respond

    @expo-probe-ff8e2b/snack-probe-c2a16 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If @expo-probe-ff8e2b/snack-probe-c2a16 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @expo-probe-ff8e2b/snack-probe-c2a16 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022972IN-MAL-2026-022973

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @expo-probe-ff8e2b/snack-probe-c2a16-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

@expo-probe-ff8e2b/snack-probe-c2a16 (npm) malicious package — MAL-2026-20314 | O3 Security