Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-8x4m-qw58-3pcx

mppx has multiple payment bypass and griefing vulnerabilities

Published
Mar 29, 2026
Updated
Mar 29, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

mppxnpm
55Kdownloads / week

Description

Impact

Multiple vulnerabilities were discovered in tempo/charge and tempo/session which allowed for undesirable behaviors, including:

  • Replaying tempo/charge transaction hashes across push/pull modes, across charge/session endpoints, and via concurrent requests
  • Performing free tempo/charge requests due to missing transfer log verification in pull-mode
  • Replaying tempo/charge credentials across routes via cross-route scope confusion (memo/splits not included in scope binding)
  • Manipulating the fee payer of a tempo/charge handler into paying for requests (missing sender signature before co-signing)
  • Bypassing tempo/session voucher signature verification
  • Piggybacking off existing tempo/session channels via settle voucher reuse and weak channel ID binding
  • Performing free tempo/session requests by exploiting channel reopen without on-chain settled state
  • Accepting deductions on finalized tempo/session channels
  • Bypassing payment on free routes via method-mismatch fallback
  • Griefing tempo/session channels via force-close detection bypass (closeRequestedAt not persisted)

Patches

Fixed in 0.4.8.

Workarounds

There are no workarounds available for these vulnerabilities.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmppxall versions0.4.8

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mppx. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update mppx to 0.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8x4m-qw58-3pcx is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-8x4m-qw58-3pcx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8x4m-qw58-3pcx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Multiple vulnerabilities were discovered in `tempo/charge` and `tempo/session` which allowed for undesirable behaviors, including: - Replaying `tempo/charge` transaction hashes across push/pull modes, across charge/session endpoints, and via concurrent requests - Performing free `tempo/charge` requests due to missing transfer log verification in pull-mode - Replaying `tempo/charge` credentials across routes via cross-route scope confusion (`memo`/`splits` not included in scope binding) - Manipulating the fee payer of a `tempo/charge` handler into paying for requests (missing sender
O3 Security · Impact-Aware SCA

Is GHSA-8x4m-qw58-3pcx in your dependencies?

O3 detects GHSA-8x4m-qw58-3pcx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works