


Pro-Israel Group Claims Major Cyberattack on Iran's Cryptocurrency Exchange
The hacking group Predatory Sparrow claims responsibility for draining $90 million from Iran's Nobitex exchange amid escalating cyber tensions between Israel and Iran.
Overview
- Predatory Sparrow, a pro-Israel hacking group, drained $90 million from Iran's Nobitex cryptocurrency exchange.
- The hack involved funds being taken from Nobitex's hot wallet, confirmed by blockchain analytics firm Elliptic.
- This incident is part of ongoing cyber hostilities between Israel and Iran, marked by mutual attacks.
- Iranian researcher Hamid Kashfi reported that Sepah's banking services were disrupted due to these cyberattacks.
- The attacks have caused significant disruption for Iranian civilians, limiting their access to funds and banking services.
Content generated by AI—learn more or report issue.

Get both sides in 5 minutes with our daily newsletter.
Analysis
Emphasizes the ongoing cyberwar and military conflict between Israel and Iran, highlighting significant attacks.
Articles (3)



FAQ
The cyberattack on Nobitex involved unauthorized access to its hot wallet infrastructure, resulting in the theft of tens to hundreds of millions of dollars. The attack was claimed by the pro-Israel hacking group Predatory Sparrow, also known as Gonjeshke Darande.
The hack on Nobitex is part of ongoing cyber hostilities between Israel and Iran. Predatory Sparrow targeted Nobitex alleging it facilitated sanctions evasion and supported the Iranian regime. This incident reflects the escalating cyber war between the two nations.
Following the hack, Nobitex suspended its services, and its website and app were taken offline temporarily for an internal investigation. The company assured users that the majority of assets were safe in cold storage and that it would compensate for the damages.
Nobitex has stated that it will compensate for the damages through its insurance fund and internal resources. Users' assets held in cold storage remain secure, and the company is working to resolve the issue.
History
- 6d3 articles