0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 - Eth

Threat entity extracted from intelligence sources

Frequency
2
occurrences
First Seen
May 31, 2026
Last Seen
May 31, 2026

0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 is an eth tracked by ThreatCluster, appearing in 1 threat cluster built from 2 intelligence report mentions.

0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 is a eth tracked across 1 threat cluster and 2 intelligence report mentions on ThreatCluster. First observed May 31, 2026; most recent activity May 31, 2026.

Related Threat Clusters

  • HongCoin Investors Recover $2 Million After Nine-Year Lockup

    A security researcher named Florent discovered an integer-overflow bug in the HongCoin ICO smart contract, which had locked approximately 1,003 ETH (around $2 million) since 2016. The bug prevented refunds to investors…

    4 articles · Updated June 1, 2026

Recent Intelligence Reports

  • HongCoin ICO Recovery: How a Decade-Old Bug Was Fixed and $2M Was Reclaimed — Valuethemarkets · May 31, 2026
  • HongCoin investors recover $2M in locked ETH after nine years — Cryptobriefing · May 31, 2026

Frequently asked questions

What is 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9?

0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 is an eth tracked by ThreatCluster, appearing in 1 threat cluster built from 2 intelligence report mentions.

Is 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 still active?

The most recent intelligence report mentioning 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 on ThreatCluster is dated May 31, 2026.

What is 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 associated with?

Across ThreatCluster reporting, 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 most frequently co-occurs with Integer Overflow, Ethereum, Cwe-190 - Integer Overflow Or Wraparound, OpenZeppelin SafeMath, Solidity.

What are the latest developments involving 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9?

The most significant recent cluster is “HongCoin Investors Recover $2 Million After Nine-Year Lockup” (4 articles · Updated June 1, 2026). 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 appears across 1 threat cluster in total, listed above with sources.

How much reporting does ThreatCluster have on 0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9?

0x9fa8fa61a10ff892e4ebceb7f4e0fc684c2ce0a9 appears in 2 intelligence report mentions across 1 deduplicated threat cluster, aggregated from 17,000+ monitored sources.

CVSS v3.1 Breakdown