A monitoring script loaded from DebugBear’s CDN contained code to find an existing Polymarket trading client, inspect balances, sell positions or transfer shares, and route funds to the collector. The code was designed to use the logged-in session’s existing trading client and signing access. DebugBear acknowledged a security incident and asked customers to remove its RUM embed. The vendor’s original point of compromise remains undisclosed.
The collector has a current leaderboard label: retr544.
Polymarket’s own leaderboard returns this name for the main collector, 0x3f991…ffc18. An older Gamma response used tre54355 via a proxy binding. The current response has no user ID, so a same-user rename is unproven.
X now explicitly marks all three incident posts as author-deleted.
Fresh platform responses confirm author deletion for the original loss claim and frontend followup. A separate preserved rescue post says he moved roughly $700k to a friend who runs bots with him. That screenshot is marked edited; the version history is unknown.
Scroll to move through the chart. Use + to enlarge it. All wallet addresses are written in full inside the map.
03
Car: the older links and the latest transfer.
Another shared recipient.
Car sent 111 pUSD to 5mTraderYes on August 6. E044 sent it 333 pUSD the next day. The recipient then sent 537 pUSD to 0x6d132…a64be. All three signatures recover to their respective known keys.
E044 also funded Car and lolzzzlol before the incident. These are proven financial links. Car’s control of E044’s key has not been established.
The 750,000 pUSD transfer came back.
Car sent 750,000 pUSD to established recipient lolzzzlol during the incident. Later, 753,333 pUSD returned. Those funds cannot be counted as an outstanding $750k theft. His forced-sale claim needs a separate valuation: the chain verifies rapid liquidation, but gross proceeds do not measure the loss.
The new history closes a longer funding chain.
May 16:3e837…c2132 sent 22 USDC on Arbitrum through an intermediary and Relay. The route ended as the first 22 pUSD credit to 6d132…a64be. Four successful receipts and the matching bridge settlement bind the route.
May 17: Car put 111 pUSD through Relay to that same wallet. It received 111 native USDC, swapped it into USDC.e, then minted 110.981860 pUSD. Car’s actual signature and the recipient’s signed conversion batches are verified.
August: Car’s 111 pUSD was the first cash seed into 5mTraderYes. E044’s 333 pUSD was its only other external canonical collateral credit. The wallet also received 710 pUSD from position redemptions, spent 616.927670 pUSD in markets and sent 537 pUSD to 6d132, leaving 0.072330 pUSD. All 26 collateral receipts reconcile.
The two recipient wallets use distinct owner keys. We recovered all 17 explicit batch authorizations: 12 for 6d132 and five for 5mTraderYes. Their funding relationship is established; Car’s control of those keys remains unproven.
Older Ethereum link: gas in, 150 USDC back
On January 22, 2025, already-known funding lead 46c11…40650 sent Car’s signer 0.007 ETH. Forty-eight seconds later, Car’s key signed its only ordinary Ethereum transaction, transferring 150 USDC from his Ethereum proxy to that gas funder. The route is independently verified. It is historical activity, with no verified attacker connection.
We checked 404 direct settlement counterparties across 920 fills in the selected 82 SELL receipts. None of their wallet or claimed signer addresses exactly matched the 86-address Car lead set, its 344 derived addresses, the ten known attacker endpoints or the additional verified funding keys. Those third-party signer fields were not independently recovered.
The direct same-token BUY subset has 326 buyers, covering 518,814.839670 pUSD of trade consideration between 17:16:10 and 17:17:40 UTC. This excludes complementary-token settlement paths and Car’s maker-side sales. Every buyer/transaction group reconciles against genuine cash and share transfers.
3f701 1,526.93 USDT→Across bridge Base USDC→Captured payment 1,511.6607 net→Pooled sweep Coinbase 14 tag
NEW PROVIDER LEAD
The operator and fee pair match a Coinbase-hosted checkout path.
A public repository’s preserved checkout-challenge extract contains the exact payment operator, collector, 1% fee and fee address seen here. Coinbase’s public page confirms that separate historical session’s amount and receiver; DefiLlama independently attributes the operator to Coinbase Business. The live Coinbase page does not publish the operator/fee pair, so this is corroborated provider attribution. The incident merchant and customer remain unidentified.
The bridge signature recovers to the attacker-linked 3f701 key and commits to the amount, Base chain and 1332 recipient. On Base, a separate key authorized a Commerce payment. Capture paid 1,511.6607 USDC to receiver 5638 and charged a 15.2693 USDC fee.
The receiver’s next sweep sent 2,267.694 USDC to an address explorers label Coinbase 14. The sweep included 756.0333 USDC already there. It reaches a service address; it does not identify an exchange customer or prove that the payment recipient belongs to the attacker.
All nonzero tracked material balances · chain by chain
Balances in the ten-address tracked cluster at each pinned cutoff. Position-token inventories are outside this table.
Seven-chain review: Ethereum, Polygon, Base, Optimism, Arbitrum, BNB Chain and Avalanche. First six chain snapshots are 17:46:23–31 UTC; Avalanche is 17:56:07 UTC. Major reviewed attacker holdings are unchanged. Optimism’s 0.360967751344140708 ETH remainder reconciles exactly to its bridge receipts and fees. Open provenance ↗
This frozen collector-based ledger records pUSD redemptions and position transfers. Its amounts describe observed transfers, before refunds; position tokens are listed separately and are not assigned a dollar loss here. It is not an exhaustive incident-wide victim count.