BTCPay Server: Bitcoin outflows and unresolved endpoints

ChainBounty · Bitcoin · Activity recorded from 30 October to 6 November 2026 UTC · SentinelTX CASE-ASYNCEB6, 7 November 2026

The Bitcoin address reported in the BTCPay Server hot-wallet incident distributed funds to 20 unlabeled first-hop counterparties in the report’s retained first-hop set. SentinelTX’s report records 19.39799626 BTC across that retained set, including individual legs of 5.5 BTC and 4.71 BTC. These are gross address outflows, not an established incident loss or cash-out total.

The distinction matters. The report documents transaction movements but does not establish who controlled the recipients, whether every payment was theft proceeds, or where the funds ultimately reached a custodial service. Small receipts continued on 6 November, and the reported address held 0.11396900 BTC at the report’s balance read. Neither observation, on its own, resolves the incident’s scope.

1. What the report follows

The reported incident concerns BTCPay Server hot wallets on servers running version 2.4.1 or earlier. A hot wallet keeps the keys needed to spend funds on the server. The Bitcoin address examined here is associated with the incident in the reporting cited by SentinelTX; that association does not establish that every transaction belongs to the incident.

This analysis covers the Bitcoin movements documented in SentinelTX’s 7 November 2026 report. Litecoin activity is outside its scope and is not included in any Bitcoin figure.

• Role / scope: S0: reported Bitcoin destination — Report description: bc1p0f7wmcnesrapznymf9ljdn04pudgmh96sqtrm9vmgqxdh666fh8qvn63r7. Starting address; vendor attribution remains reported.
• Role / scope: R1: largest retained first-hop leg — Report description: bc1qn3fze9w3c0m38y84v76qr2z5dz9cjx0hz4aeva. Received 5.5 BTC; no entity attribution.
• Role / scope: R2: second-largest retained first-hop leg — Report description: bc1q8hyw6c47t4cskvn655csdc8ym7wc7tcnj6ws4j. Received 4.71 BTC; no entity attribution.
• Role / scope: Network — Report description: Bitcoin only. The Litecoin address is context, not part of this trace.
• Role / scope: Recorded scope — Report description: Selected timestamped movements span 2026-10-30T13:45:55Z to 2026-11-06T23:54:17Z. Coverage is incomplete.
• Role / scope: Coverage limit — Report description: The retained outbound set contains 20 first-hop counterparties. No labeled cash-out endpoint is established.

Source: SentinelTX CASE-ASYNCEB6, pp. 4–5, 13–17 and 23–24. Address labels S0, R1 and R2 are reading aids for this article, not entity attributions.

2. Twenty retained first-hop payments

The report’s chronology records first-hop outbound payments between 30 October and 2 November. Six transactions are itemized with block, input/output and fee details. Their counterparty legs total 14.7891317 BTC. Fourteen further retained recipients total 4.60886456 BTC, giving the report’s 20-counterparty total of 19.39799626 BTC.

The 20-counterparty set is a partial record of first-hop movements, not a complete inventory of payments during the period.

The largest retained legs

The 5.5 BTC leg, E1, was recorded at 17:06:47 UTC on 1 November, in block 974153. The 4.71 BTC leg, E2, followed at 22:29:40 UTC in block 974185. Both appear as verified in the PDF’s Path Routing Evidence. That status concerns the retrieved transaction and its named addresses; it does not establish the identity or authority of the signer.

• Selected leg: E1 → R1 — Counterparty amount and timing: 5.5 BTC · 1 November 2026, 17:06:47 UTC · block 974153
• Selected leg: E2 → R2 — Counterparty amount and timing: 4.71 BTC · 1 November 2026, 22:29:40 UTC · block 974185
• Selected leg: E3 → R3 — Counterparty amount and timing: 1.3 BTC · 1 November 2026, 16:42:26 UTC · block 974150
• Selected leg: E4 → R4 — Counterparty amount and timing: 1.29504468 BTC · 2 November 2026, 00:53:51 UTC · block 974195
• Selected leg: E5 → R5 — Counterparty amount and timing: 1.11506206 BTC · 1 November 2026, 16:14:14 UTC · block 974146

Figure 1. The five largest retained first-hop counterparty legs, shown on a common BTC scale. This selection is not an incident-loss total.

Color key: Slate groups comparable Bitcoin amounts; color does not identify ownership or risk.

Address / role key: Chart labels L1–L5 correspond to article recipients R1–R5, respectively. These are unlabeled first-hop counterparties; their full addresses and selected transaction records appear in the reference appendix.

Source: SentinelTX CASE-ASYNCEB6, Transaction Chronology, pp. 11–13.

3. Consolidation is visible; victim attribution remains open

Several transactions consumed many inputs. E2, the 4.71 BTC leg, used 138 inputs. E4, the 1.29504468 BTC leg, used 105. A separate single-output transaction, E6, consolidated 20 inputs into one output of 0.86902496 BTC.

SentinelTX assesses that this pattern is consistent with many small UTXOs accumulating at one collection address before redistribution. In the reported incident context, it fits a possible automated, multi-target hot-wallet drain. The qualification is essential: the report has not matched each input to an identified BTCPay instance or victim. Input count is not victim count.

Five of the six fully itemized spends had two outputs. The report assesses the smaller second outputs as probable change, not confirmed change, and does not identify their receiving addresses. It therefore does not establish whether those outputs returned to S0 or moved to new addresses. E6, by contrast, had a single output and no change output.

The distribution pattern also does not, by itself, prove laundering intent. SentinelTX explicitly allows alternatives such as service deposit addresses, OTC counterparties or wallets controlled by the same operator. Round amounts and close timing do not decide among those explanations.

4. Later receipts and the balance are different observations

The report records a partial sample of 21 receipts on 6 November, totaling 634,549 sats, or 0.00634549 BTC. This is not a complete daily inflow total.

One documented receipt, E7, transferred 0.0021017 BTC from bc1quh87wd84ansf7ucwf6arge3kaem03ar20av3vv at 23:54:17 UTC in block 974868. The sender’s identity and the payment’s connection to the incident are not established.

At 00:06:13 UTC on 7 November, a balance read against chain tip 974868 returned 0.11396900 BTC at S0. The tip’s block time was 23:54:17 UTC on 6 November. This is a balance at the reported read, not a claim about the balance when this article is read, recovered funds or a confirmed freezable amount.

Figure 2. Separate observations from the report: the retained outbound set, the partial 6 November receipt sample and the subject-address balance. These quantities are not added together or treated as a loss reconciliation.

Color key: Slate marks retained outflows, sage partial receipts and amber the balance snapshot. Labels preserve those distinctions without color; color does not indicate risk or certainty.

Address / role key: All three observations concern S0, the vendor-reported Bitcoin destination.

Source: SentinelTX CASE-ASYNCEB6, Executive Summary and Transaction Chronology, pp. 4–5 and 13–14.

5. Where the trace stops

No exchange deposit or bridge deposit is established within the examined activity. The reported address and the five largest first-hop recipients have no confirmed entity attribution. Coverage is incomplete, so the findings do not exclude other routes or later off-ramps.

The report separately lists addresses with no outbound movement in the traced set. “Terminal” in that table describes the boundary of the retained trace. It does not establish that an address is permanently unspent, a final real-world destination or a custodial account.

The continued receipts on 6 November are therefore unresolved. If they were further drains, they would matter for the duration of the incident. The report labels that interpretation unverified because the senders and circumstances have not been established. Unrelated payments to a publicly reported address remain an alternative.

6. Conclusion and the report’s next steps

The clearest result is transaction-level: the reported Bitcoin destination made the cited outbound payments, with the two largest retained legs at 5.5 BTC and 4.71 BTC. The retained chronology records 20 first-hop counterparties and 19.39799626 BTC. It does not establish that all of that value belongs to the BTCPay incident.

The next investigative steps are to match consolidation inputs to individual victims’ transactions and follow the largest recipient legs toward a named service. A freeze or KYC request would require a transaction-level deposit anchor at an identified exchange. Litecoin requires a separate investigation.

For affected operators, the report recommends preserving server logs, version information and relevant wallet records, reporting to the appropriate authorities, updating to BTCPay Server 2.4.7 and rotating keys that were present on an affected server. These are recommendations attributed to the report and its vendor/media context. They do not convert the observed address activity into a confirmed total loss or a promise of recovery.

Figure 3. The report’s conclusion: cited Bitcoin movements are recorded; total incident loss, recipient control and exchange cash-out are not established. Its next steps are victim-level input matching and forward tracing to a named venue.

Color key: Slate identifies section headings only; the written labels state findings and limits.

Source: SentinelTX CASE-ASYNCEB6, Recommendations and Conclusion, pp. 18–20.

7. Selected evidence and source notes

The records below are selected from the PDF. They are not a new on-chain audit or a complete evidence ledger. All times are UTC.

E1 — Largest retained leg

• Field: Transaction — PDF value: 53c7f20ae0b3bd65e6596300bbb5ca962fb9787d40bd8ca03635cbab1a76659e
• Field: Route — PDF value: S0 → R1
• Field: Time / block — PDF value: 2026-11-01 17:06:47 UTC · 974153
• Field: Counterparty leg — PDF value: 5.5 BTC
• Field: Inputs / outputs — PDF value: 5 / 2
• Field: Other output / fee — PDF value: 0.01962723 BTC probable change, not confirmed · 0.00001116 BTC fee
• Field: Reference — PDF value: Transaction Chronology, p. 11; Path Routing Evidence, p. 20, verified

E2 — The 138-input consolidation

• Field: Transaction — PDF value: 0753f5147dfb38fb85f4aba2f7bdfc40caa9ce466cf6273f2c02064260abe0c9
• Field: Route — PDF value: S0 → R2
• Field: Time / block — PDF value: 2026-11-01 22:29:40 UTC · 974185
• Field: Counterparty leg — PDF value: 4.71 BTC
• Field: Inputs / outputs — PDF value: 138 / 2
• Field: Other output / fee — PDF value: 0.00019156 BTC probable change, not confirmed · 0.00040098 BTC fee
• Field: Reference — PDF value: Transaction Chronology, p. 12; Path Routing Evidence, p. 21, verified

E3–E7 — Additional cited records

• Record: E3 — PDF value: 9e8056908abb41fe0c2800b83d36148c4f2d7c4509caf688cce55f2c2967b16e · S0 → R3 · 1.3 BTC · 2026-11-01 16:42:26 UTC · block 974150 · pp. 11 and 21
• Record: E4 — PDF value: d680e16a027e114d09a6915556c599227f7efa3a7fc20292bfcf4d06e562a557 · S0 → R4 · 1.29504468 BTC · 2026-11-02 00:53:51 UTC · block 974195 · 105 inputs / 2 outputs · pp. 12 and 21
• Record: E5 — PDF value: 3b4a4b785561d1bd6bf48afb35082d02cde2ac225cefaf3d531562c52374d462 · S0 → R5 · 1.11506206 BTC · 2026-11-01 16:14:14 UTC · block 974146 · pp. 11 and 21
• Record: E6 — PDF value: be5d005b7d7884815456b278c611294d82d6f0f7b08a966196fd77f5afd4ca08 · S0 → bc1qvc9lyhulpfup3r57nphttsdqdn8tdyxs4wp2mv · 0.86902496 BTC · 2026-11-01 17:06:47 UTC · block 974153 · 20 inputs / 1 output · pp. 12, 14 and 21
• Record: E7 — PDF value: 9af06a6fea858a23fd1f9da47982921c1084ca81c8816a77419993cf53bf9978 · bc1quh87wd84ansf7ucwf6arge3kaem03ar20av3vv → S0 · 0.0021017 BTC · 2026-11-06 23:54:17 UTC · block 974868 · p. 22, verified

Address register

• Label: R3 — Full identifier and role: bc1q8q4aqg9fyxch0k48wf2xcuqdfaqpc55un0mnsc · first-hop counterparty, no entity attribution
• Label: R4 — Full identifier and role: bc1qjdqn0tqm4agmsq5njss2snuanyqu54mjkjm8gr · first-hop counterparty, no entity attribution
• Label: R5 — Full identifier and role: bc1qwurqa0yzggsurz86mku3dqnf5pdnjkq0089vvt · first-hop counterparty, no entity attribution
• Label: Litecoin context only — Full identifier and role: ltc1qp49tmfdueyaqrmgrx0uyx4uegyygt8yt02whee · not traced in this report

Source and scope

Source: SentinelTX, CASE-ASYNCEB6, 7 November 2026, pp. 4–5, 11–20 and 20–22. This article presents selected records and assessments from that report; it is not an independent on-chain validation.

The report cites the BTCPay Server security advisory as incident context. The subject address’s association with the incident remains reported. Ownership of the recipients, victim-level linkage, total incident loss and final disposition of the funds are not established.

The first-hop outflows, partial later-receipt sample and historical balance measure different activity. They are not combined into a loss or recovery total. The coverage does not establish a complete transaction history or the beginning and end of the incident.