aeonix @aeonix_network - Twitter Profile

Pinned Tweet

6 months ago

Post-Incident Review: Aeonix Network On December 20th, Aeonix Network experienced a security incident involving the unauthorized use of administrative private keys by a project co-founder serving as Chief Technology Officer (CTO). The individual exploited privileged access to sell approximately $40,000 USD worth of ONIX tokens from the protocol’s liquidity pool, resulting in a price decline exceeding 99%. Following the sale, the proceeds were routed across chains and converted into stablecoins before being deposited into a wallet address previously used to receive the individual’s salary payments. This review summarizes confirmed facts, evidence, and the project’s current status. Incident Timeline • December 20th, 7am UTC Administrative private keys were used to execute token sales directly from the protocol’s liquidity reserves. • Immediately following Approximately $40,000 in value was sold, causing a rapid and sustained price reduction of more than 99%. • Subsequent transactions The proceeds, initially received in BNB, were routed through a multichain router. • Later transactions BNB was converted to ETH, then to USDC. • Final transfer The USDC was deposited into the same wallet address historically used to receive salary payments by the CTO. • December 21st, 2am UTC Exploit activity is determined as insider-initiated, beginning incident response procedures. Attribution and Evidence The following facts are confirmed and supported by verifiable evidence: • The transactions originated from an administrator wallet. • That wallet is operated and controlled by the project’s co-founder and CTO. • On-chain transaction records demonstrate: - Liquidity pool token sales - Cross-chain routing via a multichain router - Conversion from BNB → ETH → USDC - Deposit of USDC into a known salary payment address • No external smart contract vulnerability or third-party exploit was used. Operational Impact The co-founder and CTO operated the project’s backend infrastructure and servers. As a result: • Core product functionality is currently offline • Backend services and servers remain inaccessible • Normal protocol operations cannot resume until control and access issues are fully resolved Market Risk and Trading Warning At the time of writing: • The individual continues to hold tokens in the wallet used during the incident • Additional selling from this wallet could result in further losses Users are strongly advised not to trade the ONIX token until a resolution is reached. Incident Response and Law Enforcement Following confirmation of the incident: • The individual’s access was revoked where technically possible • Contracts and systems were secured to the extent feasible • All relevant evidence was preserved, including transaction data and internal records • A formal police report is being filed, providing authorities with supporting documentation Path Forward and Resolution Options The team is actively exploring options to: • Recover or mitigate losses where possible • Restructure or relaunch the ONIX token • Rebuild backend infrastructure under new controls Details will be shared only once plans are concrete and verifiable. Conclusion This incident was not the result of an external exploit or unknown vulnerability, but of insider misuse of administrative private keys. The facts presented are supported by on-chain evidence and internal records. We recognize the severity of this incident and the real financial and emotional impact it has on our community, partners, and users. The unauthorized actions described above caused significant losses, operational disruption, and a profound erosion of trust. Further updates, including on-chain evidence, will be shared as material developments occur. Until then, our focus remains on safeguarding users, supporting the investigative process, and working toward a responsible path forward.

3

4

0

342

aeonix

@aeonix_network

Last Seen Users on Sotwe

Trends for you

Most Popular Users