Pacific

Standard

Rewards

Time

<p>Cyberattacks on decentralized networks are not uncommon and this time the affected one is Io.net. It has faced a cybersecurity breach recently which affected its GPU metadata. Though the attack took place, there hasn’t been much harm to the network and it remains robust.&nbsp;</p>
<h2 class="wp-block-heading" id="gpu-metadata-attack-on-io-net">GPU metadata attack on Io.net</h2>
<p>Io.net has faced a cybersecurity breach recently. The mentioned DePIN (decentralized physical infrastructure network) faced a breach related to user ID tokens. Some malicious elements were involved in the use of these tokens to execute an SQL injection attack.&nbsp;</p>
<p>The result of the attack was some unauthorized changes in the device metadata. The affected area was the GPU’s network’s metadata. Though the unauthorized changes took place, these didn’t go unheeded. As soon as the chief security officer of the network Hushky.io became aware of the changes, they responded to it.</p>
<p>The CSO shared details regarding the remedial actions which included some security upgrades. Furthermore, they cleared uncertainty regarding further harm as the damage has been controlled timely. As per the available information from the <a href="https://www.cryptopolitan.com/io-net-ai-ecosystem-filecoin-integration/" rel="noopener noreferrer nofollow">Io.net</a> security team, the GPU’s actual hardware hasn’t been affected.</p>
<p>There are multiple robust layers of security in place for the mentioned DePIN. These security layers ensure that the GPU hardware isn’t affected by any unauthorized changes. The security team was alerted at 1:05 AM Pacific Standard Time as there was a surge in write operations to the API.&nbsp;</p>
<h2 class="wp-block-heading" id="uncertainty-and-subsequent-fears-regarding-the-security">Uncertainty and subsequent fears regarding the security</h2>
<p>The security team responded with the implementation of SQL injection and the logging of unauthorized change attempts. Furthermore, a specific OKTA and Auth0 solution were deployed to address the problems. These changes took place in order to address the vulnerabilities related to the universal tokens.&nbsp;</p>
<p>The unfortunate fact about these changes is the coincidence with the rewards program. As a result of the implementation of the security update, the supply-side participants decreased. Furthermore, the number of active GPU connections decreased from 0.6 million to 0.1 million.&nbsp;</p>
<p>In order to tackle the problem, <a href="https://io.net/" rel="noopener noreferrer nofollow" target="_blank">Io.net </a>has announced Ignition Rewards Season 2 in May. This rewards program will encourage supply-side participation. Also, the developers have planned including collaboration with suppliers to upgrade and restart the devices to be connected.&nbsp;</p>
<p>The breach took place as the result of the implementation of the POW mechanism to ensure that counterfeit GPUs are identified in time. The attacks escalated after the aggressive security patches caused concern and later resulted in the breach.&nbsp;</p>
<h2 class="wp-block-heading" id="response-to-the-metadata-attack">Response to the metadata attack</h2>
<p>The vulnerability has resulted in revealing user IDs. These malicious actors had compiled the leaked info in a database before the breach took place. Hushky.io, the CSO of Io.net, has responded to the metadata attack.&nbsp;</p>
<figure class="wp-block-embed is-type-rich is-provider-twitter wp-block-embed-twitter">
 <div class="wp-block-embed__wrapper">
  <blockquote class="twitter-tweet" data-width="550" data-dnt="true">
   <p lang="en" dir="ltr">So – we fucked up. <br><br>On 4/25/24 user(s) were able to use previously exposed user ID tokens to perform a SQL injection attack and mess with device metadata.<br><br>To prevent this in the future, we accelerated a deployment of auth zero authentication (OKTA) at the device level, which… <a href="https://t.co/PXdthHMU81" rel="noopener noreferrer nofollow" target="_blank">https://t.co/PXdthHMU81</a></p>— hushky.io (@0xHushky) <a href="https://twitter.com/0xHushky/status/1784390826518577330?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow" target="_blank">April 28, 2024</a>
  </blockquote>
  <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
 </div>
</figure>
<p>Hushky.io has expressed hopes regarding security and further improvements. They shared an update regarding the ongoing reviews and penetration results. As result of new changes threats can be detected and neutralized in a timely manner. Furthermore, efforts are ongoing to restore the platform’s integrity through incentives and foolproof security.&nbsp;</p>
<p>Io.net also has plans to integrate to Apple silicon chip hardware in order to improve AI and ML services.&nbsp;</p>
<h2 class="wp-block-heading" id="conclusion">Conclusion</h2>
<p>Io.net has recently faced a cyber attack recently which was countered in time. The security breach was aimed at affecting GPUs but they have remained safe due to the robust security layers. Furthermore, the CSO has announced that a livestream will take place on 28 April to show the robustness of the network.&nbsp;</p>

Io.net clears uncertainty regarding GPU metadata attack

Table of Contents

Cryptopolitan_News

Other articles published on Apr 28, 2024

Bitcoin Mining Uses Less Energy Than Traditional Banks, Study Finds

BTC Halving Could See Wild Volatility Swings — ICOs Offer Steady Gains

Bitcoin ETF Performance Tracks Underlying Asset; Says Nate Geraci

Newcomer on Layer 2: MetaLaunch Sets a Bar High

DOJ Counters Tornado Cash Developer’s Motion To Dismiss – Details

Bullish Litecoin: Mystery Signal Points To $100 Price Explosion

Join our free newsletter for daily crypto updates!