Just two weeks after the hacking incident forced Killox to halt, the platform stages a comeback and offers compensation plans to affected victims.
The comeback highlights the resilience of the platform, despite the continued, bad actors being a consistent threat to the crypto industry.
How Kiloex compensates victims for a $7 million hack
YZI Lab-backed Decentralized Exchange (DEX) revealed the news in a post on X (Twitter) and detailed how victims will be compensated.
“Some user activity was affected by the April 14, 2025 security incident in which Killox was misused by hackers. We are currently announcing solutions plans for traders, hybrid vault stakers and VIP users,” writes DEX.
In a follow-up media post, Kiloex detailed how to integrate traders, hybrid vault stakers and VIP users.
KILOEX Trader Instructions
Trader’s limit orders are cancelled while earning profits, and the suspension loss is carried out as normal. After the Killx platform is resumed, traders whose positions remain open during platform suspension remain active. However, those who have increased losses or reduced profits during this suspension will be fully compensated for this difference.
“Please close your position as soon as possible after the platform is reopened,” directed Killox.
This directive is because DEX calculates compensation based on the platform’s resume time. Therefore, traders who delay position closures can lead to differences in actual PNL (profits and losses) and reward amounts.
Kiloex Hybrid Vault Staker Instructions
Hybrid Vault Staker principals and revenue during the suspension period will not be affected. The platform recovered and completely reinjected all stolen funds into the hybrid safe.
Nonetheless, Kiloex will encourage this user cohort with a special yield campaign upon reopening, based on eligibility.
“Users receive an additional 10% APY on top of the base platform yield. Bonus yield is paid in USDT,” read the excerpt from Medium Post.
Instructions for KILOEX VIP users
This cohort of Kiloex $7 million hack victims has +1 level upgrades excluding VIP7 users. However, all affected users, including VIP7, also get a 30-day VIP status protection period.
In particular, VIP status was determined based on real-time snapshots taken at the time of the Killx Security Incident.
Kiloex details its audit and reopening plans after consultation
Beincrypto reported that Kiloex suspended the platform after the attack, investigating the violation in cooperation with security partners and tracking stolen funds.
Like the ZKSYNC incident, we encouraged White Hat support and commissioned a bounty program to recover user assets. Following these measures and due diligence, the platform is ready to resume operations.
“Kiloex is back! Following a thorough security audit by Slowmist, we will officially resume soon,” Dex shared.
Blockchain security company Slowmist supported the report and detailed its involvement in solving the Kiloex case.
“Recently, Slowmist helped Kiloex communicate with the attacker via on-chain messages, leading to a $8.44 million recovery with stolen funds,” Slowmist wrote.
Additionally, security companies highlighted the role of on-chain messaging in recovery, presenting it as a key communication tool for blockchain, including security incidents.
Despite news about reopening and compensation, Killx’s native token has dropped by more than 5%. At the time of this writing it was trading at Coingecko for $0.0425.
Meanwhile, it is worth noting that YZI Labs (formerly Binance Labs) incubated Kiloex. Dex launched the Token Generation Event (TGE) in collaboration with Binance Wallet and Pancakeswap on March 27th.
Disclaimer
In compliance with Trust Project guidelines, Beincrypto is committed to reporting without bias and transparent. This news article is intended to provide accurate and timely information. However, we recommend that readers independently verify the facts and consult with experts before making decisions based on this content. Please note that our terms and conditions, privacy policy and disclaimer have been updated.
