0x0784d3f70784…0784d3f4

ConfirmedSecurity584 vB29 sat/vB3 min decode

CoreX Declares Bitcoin Mining Hijack Over After Hashrate Drop

CoreX said the OCEAN address fell to about 100 PH/s by Nov. 15. Pool records showed 13.7 PH/s on a three-hour average and 0.66 BTC in prospective rewards still unresolved.

CoreX Reports Bitcoin Mining Power Hijacked to OCEAN
WitnessCoreX Reports Bitcoin Mining Power Hijacked to OCEANrebcenter-moscow / pixabay

Outputs

  1. CoreX declared the attack over at 1:40 a.m. ET on Nov. 15, when the flagged address was down to about 100 PH/s.

  2. OCEAN recorded a 13.7 PH/s three-hour average versus a 1.41 EH/s 24-hour average.

  3. The flagged address showed zero blocks, zero lifetime earnings and no payouts.

  4. OCEAN estimated about 0.66 BTC in rewards for work still in the reward window, excluding transaction fees.

  5. Luxor says Commander can change settings on thousands of miners; Noirlet’s attribution remains unconfirmed.

By Nathan Brooks

CoreX declared the attack over by 1:40 a.m. ET on Nov. 15, saying the flagged OCEAN pool address had fallen to about 100 petahashes per second (PH/s).

How large was the diverted mining power?

OCEAN’s Sunday-morning statistics for that address recorded a rolling three-hour average of 13.7 PH/s, compared with a 24-hour average of 1.41 exahashes per second (EH/s), equivalent to 1,410 PH/s.

The three-hour reading was therefore roughly 1% of the 24-hour average, a gap of about 103 to 1. Neither rolling average measures the diversion’s peak hash rate or establishes the precise period during which each affected machine sent work elsewhere.

CoreX’s declaration establishes the sequence of its response, not the exact start and end of every machine’s diversion. CoreX has not confirmed the number of physical machines involved, and OCEAN cautions that a worker does not necessarily correspond to one machine.

What does this change for miners and mining hosts?

The immediate operational consequence was that participating machines performed work credited to another Bitcoin address rather than their owners’ addresses. OCEAN’s setup instructions describe the mechanism: miners connect to the pool and use a Bitcoin address as their username.

Changing that configuration changes which address receives credit for mining work. Credit follows the configured username rather than the physical location of the miner. Pool statistics can therefore show work without establishing which owner receives its eventual reward.

For mine owners and hosts, pool-address configuration and access to fleet-management controls are material to revenue attribution and operational security. CoreX said it believed it had isolated the program used but declined to name it: “I have my assumptions but I won't post who or what.”

An X account using the name Noirlet claimed that its entire farm had been affected and blamed Luxor Commander. No independent confirmation supports that attribution, and the claim does not establish a breach of Luxor’s software.

Luxor describes Commander as fleet-management software capable of changing pool settings on thousands of miners in one operation. That scale explains why access to management tools matters to miners and hosts. It does not make Commander the confirmed entry point in this incident.

Can the flagged address still collect rewards?

The flagged address’s OCEAN page showed zero blocks found, zero lifetime earnings and no payouts. A separate mempool.space record showed no confirmed or pending transactions for the address.

The wallet and pool records answer different questions at this stage: one shows whether Bitcoin has moved, while the other tracks mining work that may still qualify for a later reward.

OCEAN’s dashboard estimated about 0.66 BTC in rewards for work still inside its reward window, excluding transaction fees. The figure represents neither a payment already received nor a verified total for affected miners’ losses.

Under OCEAN’s TIDES reward system, accepted mining work remains eligible for a share of subsequent block rewards while it sits within the relevant window. The flagged address could therefore receive rewards when the pool next finds a block, even if most redirected machines have already left.

The next concrete checkpoint is OCEAN’s next block: if the accepted work remains inside the TIDES reward window, the flagged address could become eligible for payment. CoreX’s belief that it had isolated an unnamed program does not resolve that payout question or identify a confirmed initial point of access.

via cryptonews.net (Source)

More from Nathan Brooks

Nathan Brooks

Show full bio

Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,230 articles