Myriad Voids 10 Markets After Wallet Compromise and Sets Refund Terms

Ten markets lose their reported outcomes

The compromised wallet was internal to Myriad, according to the platform's explanation carried by the two outlets. The reports say attackers used it to manipulate outcomes in 10 markets on BNB Chain. Myriad then voided those markets and announced a refund process covering both long and short positions. The stated remedy therefore reaches holders on either side of an affected market, rather than only traders whose side appeared to lose after the manipulation.

The reported examples cover several kinds of bets: whether Base will issue a token in 2026, the U.S. midterm elections, crypto and commodity prices, and whether George Russell will win the 2026 Formula One drivers' championship. These are examples from the affected set. The reports do not provide a complete market-by-market inventory with identifiers, position sizes and settlement transactions. Odaily lists the affected topics.

A holder should match a position to the exact market question before treating it as covered. A reference to commodity prices does not identify every commodity market on the platform. Equally, a reference to Base concerns a prediction about a possible token event; it does not establish that Base has announced a token. Keep the wording of the prediction separate from news about its subject.

The same care applies to a sports or election contract. A platform's decision to void a prediction market describes the handling of that contract. It does not determine the real-world result of the race or election. A screenshot of an affected outcome, without the market question and the platform's corrective notice, leaves out the context needed to understand what happened.

The refund reference is the price before the attack

Myriad's reported plan uses the last price for each outcome before the attack. That reference is the central detail for checking a refund. It is a different reference from whatever value a manipulated result briefly displayed. The reports also say false profits already claimed will be deducted. Both parts belong in the calculation; reading only the recovery statement leaves out the adjustment that may affect a particular holder. PANews describes those terms.

Start with the affected market name, the outcome held and the quantity recorded in your account. Save any visible record of the relevant pre-attack price. Preserve the transaction history associated with the position, including a claimed payout if one appears. These records let you compare a later credit with the terms Myriad described, without assuming the amount from a manipulated market display is still the amount owed.

The source reports do not supply a worked calculation for an individual account. They also do not specify an exact snapshot timestamp for every market. A reader cannot calculate a reliable personal refund from the headline alone. If the platform later supplies a detailed breakdown, compare its reference price, position quantity and deduction separately. Do not invent a missing price to make the account reconcile.

For a holder who collected no payout from the manipulated result, the useful comparison is between the recorded position and the credited refund. For a holder who did collect such a payout, retain that transaction alongside the refund. The reported deduction rule makes that history relevant. This is a way to examine the announced terms, not confirmation of how any particular wallet has been assessed.

Recovery and payment are separate checks

Myriad says it recovered the funds and that the attacker withdrew none. The available reports carry that statement from the platform. They do not provide an independently verified accounting of the recovered amount or a transaction list proving completion of every refund. Keep the attribution when describing the recovery. Odaily reports Myriad's recovery statement.

PANews adds that refunds will come from the recovered funds and the affected market liquidity pools. It says users do not need to apply and that payments will be deposited automatically into their wallets. Those details describe the announced funding and delivery method. The report gives no universal payment deadline or verified completion percentage. An automatic process can still require a holder to compare the eventual credit with the position record.

Check the wallet you used for the affected market and its transaction history. When a credit appears, retain its transaction identifier and the asset shown. Compare the market's refund entry, if available, with the wallet receipt. A platform notice that funds were recovered answers a different question from a wallet record showing that your payment arrived.

If the records do not match, prepare a concise account of the discrepancy: exact market question, affected outcome, recorded quantity, any earlier payout and the later credit. Use the support route already available through the platform you used. The reports do not name a new claims portal, a special refund token or a fee that users must pay to unlock compensation. Those missing terms should not be supplied by an unsolicited message.

The third-party library remains unnamed

Myriad attributes the key exposure to a vulnerability in an unnamed third-party library used by its backend services. The platform says the exposure happened several weeks before the incident. That is the stated explanation for how the internal wallet became compromised. The reporting does not name the library, identify a software version or provide a full technical reconstruction. PANews carries the backend-library explanation.

The timing deserves careful wording. October 26 is the incident date described by the platform; the earlier exposure is described only as occurring several weeks before. Neither report provides an exact time for the compromise or the refund-price cutoff. An article publication time cannot fill either gap. Odaily's page displays its report at 08:34 SGT on October 28, which is a news timestamp rather than the moment the wallet was exposed.

For an affected trader, the technical question worth following is whether a later incident report explains how the vulnerable service reached the internal wallet and how the affected markets were identified. The current sources do not answer those questions. They also do not establish a compromise of BNB Chain itself or theft from every Myriad user's personal wallet. Keep the incident scope tied to the internal wallet and the 10 markets described.

A broader claim about all prediction-market infrastructure would require broader evidence. Here, the actionable information concerns a defined set of voided positions and the platform's proposed refund reference. A security explanation can develop later without changing the need to retain the position history now.

What holders can do with the information available

Open the affected position through the platform interface you already use. Record the market's full question and any notice that says it was voided. Match the connected wallet address to your own transaction records before comparing balances. The useful evidence is the record of your position and any payment, not a repost of the headline.

Then check the reference used for the refund. The plan described by Myriad points to the last outcome price before the attack and a deduction for false profits already claimed. If your account shows a different reference, preserve that display and ask for the calculation. Avoid submitting another trade merely to reproduce an old screen; a new position would not document the old one.

For someone who also holds BNB or other assets in an exchange account, this incident report alone provides no basis for assuming that account is affected. The cited accounts concern Myriad's internal wallet and markets on BNB Chain. Before moving assets, identify the service and position actually named in your records. An exchange balance and a prediction-market position require their own checks.

If you are organizing the incident alongside other holdings, the market calendar can serve as a place to start reviewing dated events. Use the news section to separate later reporting from the original recovery claim. Neither page replaces the affected wallet's transaction history when checking a refund.

Questions raised by the refund announcement

Do both sides of a voided market receive a refund?

The reported plan covers long and short positions at the last pre-attack prices for the relevant outcomes. False profits already collected are deducted. The sources do not publish a personal refund amount for each holder.

Must users submit an application?

PANews says the announced process is automatic and that funds will be deposited into users' wallets without an application. Verify receipt in the wallet used for the affected position. The available account does not establish that every payment is complete.

Did the attacker withdraw funds?

Myriad says the attacker withdrew none and that the funds were recovered. This remains an attributed platform statement in the reporting reviewed here; no complete independent transaction reconciliation is provided.

Which detail is still missing for a holder?

A complete list of affected market identifiers, exact snapshot times, the total refund amount and a confirmed final payment deadline are absent from the available reports. Those are concrete items to look for in a later refund breakdown or incident report.