AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 28 Monero

feat: integrate `getOnramperSignature` method and add support for retrieving Onramper signature (#2553)

Public commit record

What the developer wrote

Authored by Konstantin Ullrich

98/100 · Strong
feat: integrate `getOnramperSignature` method and add support for retrieving Onramper signature (#2553)

* feat: integrate `getOnramperSignature` method and add support for retrieving Onramper signature

* fix: make `getOnramperSignature` call asynchronous

* fix: normalize networkWallets parameter to lowercase [skip ci]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This commit adds a new step when a user buys cryptocurrency through the Onramper service. Before opening the Onramper checkout page, the app now sends the user's chosen crypto address to a Cake Wallet server (exchange-helper.cakewallet.com) to request a signature. That signature is then included in the checkout URL. The change also normalizes the blockchain network name to lowercase. There is no direct evidence in the commit of a vulnerability, but it introduces a new network call that handles a real user address and an API key, which is worth reviewing for privacy and trust assumptions.

Recommended action

Treat this as a routine feature commit that warrants a focused security review rather than an incident response. Verify that exchange-helper.cakewallet.com uses TLS with certificate pinning, that the API key is scoped and rotated, that the returned signature is validated before use, and that the server does not log or retain user addresses. Confirm whether Onramper requires this signature for fraud/integrity purposes and document the trust boundary. No immediate patch is indicated by the diff alone.

Security signals we found

01

New outbound network request to a Cake-controlled helper API carrying a user crypto address and an API key

02

Third-party/fiat-ramp integration now depends on a server-side signature whose generation logic is not visible in the repository

03

API key retrieved from app secrets and sent in a request header

04

No visible signature validation or certificate pinning for the helper endpoint

05

Lowercase normalization of networkWallets parameter, likely to match Onramper's expected format

Risk score

Why this scored 28/100

Our methodology →
Potential impact 4/30
Exploitability 5/25
Stealth signal 6/15
Affected reach 5/15
Confidence 5/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.