"
Then: "Stolen assets include aWBTC, DAI, WBTC, ETH, aUSDC, sDAI, USDS, cbBTC, and several other tokens. PeckShield, another security firm, put the loss at about $25.6 million, including roughly $6.3 million in aWBTC, $5.1 million in DAI, $4.7 million in WBTC, and $2.6 million in ETH. The attacker swapped part of the stolen holdings into 20 million DAI and about 3,000 ETH (worth about $5.64 million), with funds spread across four addresses."
Indonesian: "Aset yang dicuri termasuk aWBTC, DAI, WBTC, ETH, aUSDC, sDAI, USDS, cbBTC, dan beberapa token lainnya. PeckShield, firma keamanan lain, memperkirakan kerugian sekitar $25,6 juta, termasuk sekitar $6,3 juta dalam aWBTC, $5,1 juta dalam DAI, $4,7 juta dalam WBTC, dan $2,6 juta dalam ETH. Penyerang menukar sebagian aset curian menjadi 20 juta DAI dan sekitar 3.000 ETH (senilai sekitar $5,64 juta), dengan dana tersebar di empat alamat."
Next: "
The earlier phishing attack
" -> "
Serangan phishing sebelumnya
"
Then: "In the first incident, the same wallet lost 9,579 stETH worth $15.54 million and 4,851 rETH worth $8.51 million in a phishing attack. That brought the total to about $50.3 million across both events. The difference between Lookonchain's and PeckShield's figures comes down to how they value the assets they track."
Indonesian: "Pada insiden pertama, dompet yang sama kehilangan 9.579 stETH senilai $15,54 juta dan 4.851 rETH senilai $8,51 juta dalam serangan phishing. Itu membawa total menjadi sekitar $50,3 juta di kedua peristiwa tersebut. Perbedaan antara angka Lookonchain dan PeckShield disebabkan oleh cara mereka menilai aset yang mereka lacak."
Next: "
A broader problem with key misuse
" -> "
Masalah yang lebih luas dengan penyalahgunaan kunci
"
Then: "Lookonchain also flagged a separate case of address poisoning where a victim lost $100,000 by copying a lookalike wallet address. A Blockaid report found hackers stole $1.1 billion across 212 incidents in the first half of 2026, with privileged key misuse accounting for roughly $790 million — about 75% of all funds stolen. Monthly incident counts climbed from 18 in January to 57 in June. North Korea-linked hackers accounted for about 55% of all funds stolen in the period, roughly $609 million, but nothing ties TLBL's case to that cluster specifically."
Indonesian: "Lookonchain juga menandai kasus terpisah tentang keracunan alamat (address poisoning) di mana seorang korban kehilangan $100.000 karena menyalin alamat dompet yang mirip. Laporan Blockaid menemukan bahwa peretas mencuri $1,1 miliar dalam 212 insiden pada paruh pertama tahun 2026, dengan penyalahgunaan kunci istimewa menyumbang sekitar $790 juta — sekitar 75% dari semua dana yang dicuri. Jumlah insiden bulanan naik dari 18 pada Januari menjadi 57 pada Juni. Peretas yang terkait dengan Korea Utara menyumbang sekitar 55% dari semua dana yang dicuri pada periode tersebut, sekitar $609 juta, tetapi tidak ada yang mengaitkan kasus TLBL dengan kelompok tersebut secara spesifik."
Note: "address poisoning" might be translated as "keracunan alamat" but it's a technical term; we can keep it in parentheses or explain. I'll use "keracunan alamat" as it's common.
Next: "The attacker's funds remain spread across four addresses, and it's unclear if any recovery efforts are underway. The case adds to a growing list of incidents where private key compromise, not smart contract bugs, is the entry point."
Indonesian: "Dana penyerang tetap tersebar di empat alamat, dan tidak jelas apakah ada upaya pemulihan yang sedang dilakukan. Kasus ini menambah daftar insiden yang semakin panjang di mana kompromi kunci pribadi, bukan bug kontrak pintar, menjadi titik masuknya."
Now we need to put it all together in the JSON structure. Also translate meta description.
Original meta: "A crypto whale lost over $26 million in a second major theft, two years after a $24 million phishing attack. Private key compromise suspected."
Indonesian: "Seekor paus kripto kehilangan lebih dari $26 juta dalam pencurian besar kedua, dua tahun setelah serangan phishing $24 juta. Kompromi kunci pribadi diduga terjadi."
But we can make it more natural: "Paus kripto kehilangan lebih dari $26 juta dalam pencurian besar kedua, dua tahun setelah serangan phishing $24 juta. Diduga terjadi kompromi kunci pribadi."
I'll go with that.
Now ensure the content is wrapped in tags. The original had and closing. We'll keep that.
Let's write the JSON.
Note: The numbers and amounts should be preserved exactly, but we can use commas for thousands as in Indonesian? Actually, Indonesian uses periods for thousands and commas for decimals, but in financial contexts, often they use the same as English? To be safe, we'll keep the original formatting: $26 million, $50.3 million, etc. But in the translated text, we might write "26 juta dolar" but the original has "$26M" - we can keep the dollar sign and numbers as is, but in Indonesian we often write "US$26 juta" or just "$26 juta". I'll keep it as "$26 juta" for consistency.
Actually, the original uses "$26M" but in the text it's "$26 million". We'll translate "million" as "juta". So "$26 juta" is fine. For decimals like $50.3 million, we'll write "$50,3 juta" using comma as decimal separator? In Indonesian, decimal comma is used, but in financial contexts with dollars, often they use period? To be safe, we can keep the original decimal point. But the instruction says "Maintain the exact meaning and tone" and "Keep all facts, numbers, and data accurate". So we should keep the numbers exactly as they appear: $26 million, $50.3 million, etc. But in Indonesian, we might write "26 juta dolar" but we can keep the symbol and number. I'll keep the dollar sign and the number with the decimal point as in original, but change "million" to "juta". So "$26 juta" and "$50,3 juta"? Actually, the original uses a period for decimal: $50.3 million. In Indonesian, the decimal separator is comma, but for currency amounts, sometimes they use period. To avoid confusion, I'll keep the original format: $50.3 million -> "$50,3 juta" but that might be odd. Better to keep the number as is: "$50.3 juta
