Io.net Attack Has Been Fixed, Protocol Returns To Normal Operation

Key Points:

  • Husky.io addresses io.net attack, requiring node updates and impacting reward program snapshots.
  • Fake GPU surge prompts io.net’s security efforts, restoring network functionality after challenges.
  • Despite disruptions, io.net launches Ignition Rewards Season 2 and stays committed to development goals.
The Chief Security Officer of Solana’s DePIN io.net protocol, Husky.io, addressed an update on the metadata API attack, urging all nodes to restart and update to the latest client.
Io.net Attack Has Been Fixed, Protocol Returns To Normal Operation
Io.net Attack Has Been Fixed, Protocol Returns To Normal Operation 2

Read more: io.net Review: Notable DePIN Project In The Solana Ecosystem

Husky.io Addresses Security Breach in Io.net Attack

This move, however, clashed with the reward program snapshot time. To mitigate this, Ignition Rewards Season 2 was introduced in May to incentivize supplier participation. Collaborating directly with suppliers, efforts are underway to upgrade, restart, and reconnect to the network.

The io.net attack has been rectified, allowing the reactivation of the self-service cluster, with plans underway to develop a self-service large cluster. Enhancements in the browser interface will now clearly distinguish recently connected but unverified devices, those verified by proof of work, and devices sending active heartbeats.

Solana protocol Io.net faced a recent cybersecurity breach related to user ID tokens, resulting in unauthorized changes to the device’s metadata, particularly in the GPU network metadata. This breach occurred due to the implementation of a Proof of Work (PoW) mechanism to identify fake GPUs promptly, which inadvertently led to escalating attacks and subsequent breaches.

Read more: 5 Notable DePIN Crypto Projects You Should Know

Io.net Presses Forward with Reward Program Amidst Disruptions

Shadid revealed the company’s detection of a surge in spoofed GPUs attempting to exploit rewards—a Sybil attack. In response, io.net swiftly acted to identify and block these fraudulent devices. While this endeavor led to short-term challenges, the network infrastructure has since been restored to full functionality, albeit with a temporary reduction in GPU supply as partners rejoin.

Shadid reassured stakeholders that the io.net attack did not derail io.net’s development plans, confirming the launch of a second rewards program for suppliers from May 1st to May 30th. Despite the setbacks, Shadid affirmed the company’s commitment to its roadmap, including the forthcoming IO Cloud v2 and $IO Coin launch.

Io.net Attack Has Been Fixed, Protocol Returns To Normal Operation

Key Points:

  • Husky.io addresses io.net attack, requiring node updates and impacting reward program snapshots.
  • Fake GPU surge prompts io.net’s security efforts, restoring network functionality after challenges.
  • Despite disruptions, io.net launches Ignition Rewards Season 2 and stays committed to development goals.
The Chief Security Officer of Solana’s DePIN io.net protocol, Husky.io, addressed an update on the metadata API attack, urging all nodes to restart and update to the latest client.
Io.net Attack Has Been Fixed, Protocol Returns To Normal Operation
Io.net Attack Has Been Fixed, Protocol Returns To Normal Operation 4

Read more: io.net Review: Notable DePIN Project In The Solana Ecosystem

Husky.io Addresses Security Breach in Io.net Attack

This move, however, clashed with the reward program snapshot time. To mitigate this, Ignition Rewards Season 2 was introduced in May to incentivize supplier participation. Collaborating directly with suppliers, efforts are underway to upgrade, restart, and reconnect to the network.

The io.net attack has been rectified, allowing the reactivation of the self-service cluster, with plans underway to develop a self-service large cluster. Enhancements in the browser interface will now clearly distinguish recently connected but unverified devices, those verified by proof of work, and devices sending active heartbeats.

Solana protocol Io.net faced a recent cybersecurity breach related to user ID tokens, resulting in unauthorized changes to the device’s metadata, particularly in the GPU network metadata. This breach occurred due to the implementation of a Proof of Work (PoW) mechanism to identify fake GPUs promptly, which inadvertently led to escalating attacks and subsequent breaches.

Read more: 5 Notable DePIN Crypto Projects You Should Know

Io.net Presses Forward with Reward Program Amidst Disruptions

Shadid revealed the company’s detection of a surge in spoofed GPUs attempting to exploit rewards—a Sybil attack. In response, io.net swiftly acted to identify and block these fraudulent devices. While this endeavor led to short-term challenges, the network infrastructure has since been restored to full functionality, albeit with a temporary reduction in GPU supply as partners rejoin.

Shadid reassured stakeholders that the io.net attack did not derail io.net’s development plans, confirming the launch of a second rewards program for suppliers from May 1st to May 30th. Despite the setbacks, Shadid affirmed the company’s commitment to its roadmap, including the forthcoming IO Cloud v2 and $IO Coin launch.

Visited 228 times, 1 visit(s) today