Bitcoin mining industry rocked by AI-linked breach as hackers divert up to 13 EH/s of computing power

บทคัดย่อ:Hackers allegedly diverted 13 EH/s of Bitcoin mining power to OCEAN, redirecting rewards from thousands of machines to a single wallet.

Bitcoin mining operators faced a suspected large-scale hijacking over the weekend after thousands of machines were allegedly redirected to the OCEAN mining pool without authorization.

Related Asset Bitcoin #1 BTC · $64,525.20 24-hour change: down 0.28% Loading price history… 24H Down 0.28% 7D Down 14.44% 30D Down 20.61%

On Nov. 15, mining infrastructure provider CoreX Hosting raised the alarm that mining equipment was being redirected to OCEAN and that rewards were being assigned to a single Bitcoin address.

BTC enthusiast GalaxyMind estimated that the attack affected approximately 64,000 Bitcoin mining machines, redirecting 13 exahashes per second (EH/s) of computing power since around 8 p.m. Central Time on Nov. 14.

Blockchain security firm CoinSpect added that the redirected computing power represented approximately 1.5% of Bitcoin's global hashrate.

The incident threatened miners' earnings because the unauthorized changes directed rewards away from their intended recipients while their equipment continued consuming electricity and processing transactions.

CoreX subsequently reported that it was restoring affected miners to their original configurations and believed it had isolated the program responsible for the unauthorized changes.

The company later declared the incident over after the computing power associated with the suspicious address reportedly fell to approximately 100 petahashes per second (PH/s), down from the previously reported 13 EH/s.

Still, blockchain records show that the Bitcoin address identified in CoreX's original warning had received mining rewards. Data from OCEAN shows three payments totaling 0.24308905 BTC between Nov. 15 and Nov. 16.

One address links the alert and a block reward

Dashed line: destination named by the host. Solid line: confirmed coinbase credit to that address.

A reported destination becomes a recorded reward recipientThe CoreX report names a Bitcoin address; an OCEAN-attributed block credits the same address. The report and transaction establish different facts.15 NOVEMBER 2026

  • HOST'S REPORT · 03:08 GMT@CoreX_HostingMiners redirected to OCEANNames the payout destination

BLOCK REWARD · 17:22:50 GMT0.08088977BTCOCEAN-attributed block 975995Credits the same address

NAMED ADDRESSbc1qphuk…pcddrr

  • Earlier shares can stay eligibleTIDES shares can remain eligible across later pool blocks.Eligibility does not guarantee another payment.

The same address in a CoreX report and an OCEAN block rewardTwo separately labelled observations point to the same Bitcoin address, followed by the general TIDES eligibility explanation.15 NOVEMBER 2026

  • HOST'S REPORT · 03:08 GMT@CoreX_HostingReported miners redirected to OCEAN

NAMES THE ADDRESS

NAMED ADDRESSbc1qphuk…pcddrr

CREDITS SAME ADDRESSBLOCK REWARD · 17:22:50 GMT0.08088977 BTCOCEAN-attributed block 975995

  • Earlier shares can stay eligibleTIDES shares can remain eligibleacross later pool blocks.Eligibility does not guaranteeanother payment.

The host's report and the block record establish different facts about the same address.

The transaction does not identify the controller or prove which incident shares generated the reward.

Sources and evidence

Sources

  • @CoreX_Hosting alert
  • mempool.space address transactions
  • mempool.space address transactions
  • mempool.space block record
  • OCEAN TIDES documentation
  • Supporting facts

    • Reported statement @CoreX_Hosting reported at 03:08 GMT on Nov. 15 that miners were being redirected to OCEAN with the Bitcoin address bc1qphukp9rjfc4rcej7erpm9ae20xmtspw8pcddrr. [1]
    • At 17:25 GMT, mempool.space recorded one confirmed transaction funding the named address with 8,088,977 satoshis, or 0.08088977 BTC, and no recorded spending. [2] [3]
    • The named address's 0.08088977 BTC output was part of the coinbase transaction in block 975995, timestamped 17:22:50 GMT on Nov. 15 and labelled OCEAN by mempool.space. [3] [4]
    • OCEAN's TIDES documentation says shares inside its reward window can receive a portion of multiple pool block rewards, so a pause in hashing does not by itself end reward eligibility. [5]

    Method

    Match the exact address named in the CoreX alert to the coinbase output and OCEAN-attributed block. Diagram arrows mean names and credits, not a proven path from compromised machines to payment.

    Scope

    The transaction does not identify the controller or prove which incident shares generated the reward.

    Infographic by CryptoSlate

    OCEAN's TIDES reward system allows previously submitted mining work to qualify for payments from later blocks. Consequently, rewards can keep arriving after mining activity stops.

    Luxor confirms Commander breach, blames sophisticated AI-enabled attack

    While the central cause of the attack remains unknown, Bitcoin mining technology company Luxor confirmed that its Commander mining-management platform suffered a security breach that allowed unauthorized changes to customers' mining configurations.

    It stated:

    “Last night our internal monitoring alerted us to an unauthorized redirect of hashrate through Commander…over a dozen client accounts. Affected machines were pointed to a different pool for a limited window. No data was leaked or exfiltrated from our systems.”

    The firm's engineering team patched Commander within two hours and began restoring affected machines to their original mining pools. It also promised full compensation for the redirected computing power.

    Luxor CEO Nick Hansen attributed the compromise to a “sophisticated AI-enabled vector,” saying the attack began around 6 p.m. Pacific time on Nov. 14.

    Hansen apologized to affected customers and warned that cryptocurrency companies were facing an increasingly aggressive wave of AI-powered attacks. He said:

    “At this moment, anyone running any sort of substantial business, especially in crypto, is inundated with AI-enabled attacks. Abliterated models are running 24/7 against your entire surface, looking for a little crack, which they then use to (almost instantly) expand. This does not seem to be slowing down; rather, it's speeding up as models get better and more attackers enter the arena.”

    He revealed that Luxor had acquired dedicated GPUs to run its own modified AI models for defensive security testing and had suspended much of its new feature development to harden its infrastructure.

    Luxor has not disclosed the precise method used to compromise Commander or confirmed GalaxyMind's estimates of 64,000 affected machines and 13 EH/s.

    The company has promised a full post-mortem, which could establish how the attackers gained access, the actual extent of the disruption, and whether the reported computing power was entirely linked to its compromised platform.

ข้อจำกัดความรับผิดชอบ

มุมมองในบทความนี้แสดงถึงมุมมองส่วนตัวของผู้เขียนเท่านั้นและไม่ถือเป็นคำแนะนำในการลงทุน สำหรับแพลตฟอร์มนี้ไม่รับประกันความถูกต้องครบถ้วนและทันเวลาของข้อมูลบทความ และไม่รับผิดชอบต่อการสูญเสียใด ๆ ที่เกิดจากการใช้ข้อมูลในบทความ
บทความก่อนหน้า

บิตคอยน์คาดหวัง IPO ของ Anthropic จะเหมือนกับ SpaceX แต่ยังขาดส่วนหนึ่งของเรื่องนี้

ถัดไป

แฮกเกอร์นักขุด Bitcoin ในสหรัฐอเมริกาได้เงิน USD โดยไม่พบ block เดียวได้อย่างไร