https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?action=history&feed=atom&title=Ethereum_Classic_Github_Taken_Over 2026-07-26T07:22:48Z Revision history for this page on the wiki MediaWiki 1.39.1 https://quadrigainitiative.com/cryptocurrencyhackscamfraudwiki/index.php?title=Ethereum_Classic_Github_Taken_Over&diff=4885&oldid=prev 2023-08-20T18:25:32Z

<p>Created page with &quot;{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/ethereumclassicgithubtakenover.php}} {{Unattributed Sources}} <a href="/cryptocurrencyhackscamfraudwiki/index.php?title=File:Ethereumclassic.jpg" title="File:Ethereumclassic.jpg">thumb|Ethereum Classic</a>The official Ethereum Classic GitHub repository was taken over by an unknown individual, causing concern for the security of the project. The incident involved someone gaining admin control over the Ethereum Classic community with Classic Geth and subsequently removing all other adminis...&quot;</p> <p><b>New page</b></p><div>{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/ethereumclassicgithubtakenover.php}}<br /> {{Unattributed Sources}}<br /> <br /> [[File:Ethereumclassic.jpg|thumb|Ethereum Classic]]The official Ethereum Classic GitHub repository was taken over by an unknown individual, causing concern for the security of the project. The incident involved someone gaining admin control over the Ethereum Classic community with Classic Geth and subsequently removing all other administrators. Although this posed a significant security risk, no damage to repositories had occurred at the time. Igor Artamonov, Founder and CTO of ETC Dev, advised users to avoid downloading Classic Geth until the issue was resolved. Ethereum Classic's blockchain itself remained unaffected, and an update confirmed that ownership was restored to previous administrators and the issue was resolved.<br /> <br /> This is a global/international case not involving a specific country.&lt;ref name=&quot;redditold-11473&quot; /&gt;&lt;ref name=&quot;redditold-11474&quot; /&gt;&lt;ref name=&quot;redditold-11475&quot; /&gt;<br /> <br /> == About Ethereum Classic ==<br /> &quot;The official Ethereum Classic github has been taken over by some unknown person. This has been confirmed by Anthony, director of ETC Cooperative.<br /> <br /> Here is what happened – someone took admin control of Ethereum Classic community with Classic Geth and has removed all other administrators.<br /> <br /> This, as you can understand, is an important security issue, but so far the intruder has not done any damage to any repositories.<br /> <br /> We are in contact with GitHub and working to regain control. The user who took ownership has not made any changes to any repositories as of the time of this tweet.<br /> <br /> However, as the note indicates, please proceed with caution. https://t.co/ZrJdoyol0S<br /> <br /> — Anthony Ȼlassic (@pyskell) November 30, 2018<br /> <br /> Igor Artamonov, Founder and CTO of ETC Dev recommends users to not download Classic Geth until this issue is resolved.<br /> <br /> Interestingly, Anthony does mention that Igor did give admin control to krykoder, another Github user, so it could be Krykoder who has deleted all other admins.<br /> <br /> He adds that ETC Cooperative team is trying to establish the identity of this Github user without alerting krykoder. This is his tweet.<br /> <br /> We were attempting to do this without alerting krykoder so that he wouldn’t up and delete the repository or engage in other nefarious action. We’ve tried to establish communication with Igor and coordinate regarding this but received little response.<br /> <br /> We have backups of all repos<br /> <br /> — Anthony Ȼlassic (@pyskell) November 30, 2018<br /> <br /> Ethereum Classic blockchain is not affected by this since blockchain does not runs on the github (duh). It is the github that has been attacked. We are mentioning this since there are rumors brewing that ETC has been attacked.<br /> <br /> The team has reassured that they have backups of all repositories.<br /> <br /> Update – Anthony has tweeted that ownership of previous people has been restored and no damage was done. The new owners has given back admin rights to ex-admins.<br /> <br /> Looks like all is fine. There was a misunderstanding in ownership of the organization. The issue will be fixed now that the user is aware. https://t.co/WsrFKxqddP<br /> <br /> — Anthony Ȼlassic (@pyskell) November 30, 2018&quot;<br /> <br /> This is a global/international case not involving a specific country.<br /> <br /> The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.<br /> <br /> Include:<br /> <br /> * Known history of when and how the service was started.<br /> * What problems does the company or service claim to solve?<br /> * What marketing materials were used by the firm or business?<br /> * Audits performed, and excerpts that may have been included.<br /> * Business registration documents shown (fake or legitimate).<br /> * How were people recruited to participate?<br /> * Public warnings and announcements prior to the event.<br /> <br /> Don't Include:<br /> * Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.<br /> * Anything that wasn't reasonably knowable at the time of the event.<br /> There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.<br /> <br /> == The Reality ==<br /> This sections is included if a case involved deception or information that was unknown at the time. Examples include:<br /> <br /> * When the service was actually started (if different than the &quot;official story&quot;).<br /> * Who actually ran a service and their own personal history.<br /> * How the service was structured behind the scenes. (For example, there was no &quot;trading bot&quot;.)<br /> * Details of what audits reported and how vulnerabilities were missed during auditing.<br /> <br /> == What Happened ==<br /> The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.<br /> {| class=&quot;wikitable&quot;<br /> |+Key Event Timeline - Ethereum Classic Github Taken Over<br /> !Date<br /> !Event<br /> !Description<br /> |-<br /> |November 30th, 2018<br /> |Github Taken Over<br /> |The Ethereum Classic Github account was taken over.<br /> |}<br /> <br /> == Technical Details ==<br /> This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?<br /> <br /> == Total Amount Lost ==<br /> No funds were lost.<br /> <br /> How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?<br /> <br /> == Immediate Reactions ==<br /> How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?<br /> <br /> == Ultimate Outcome ==<br /> What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?<br /> <br /> == Total Amount Recovered ==<br /> There do not appear to have been any funds recovered in this case.<br /> <br /> What funds were recovered? What funds were reimbursed for those affected users?<br /> <br /> == Ongoing Developments ==<br /> What parts of this case are still remaining to be concluded?<br /> == Individual Prevention Policies ==<br /> {{Prevention:Individuals:Placeholder}}<br /> <br /> {{Prevention:Individuals:End}}<br /> <br /> == Platform Prevention Policies ==<br /> {{Prevention:Platforms:Placeholder}}<br /> <br /> {{Prevention:Platforms:End}}<br /> <br /> == Regulatory Prevention Policies ==<br /> {{Prevention:Regulators:Placeholder}}<br /> <br /> {{Prevention:Regulators:End}}<br /> <br /> == References ==<br /> &lt;references&gt;&lt;ref name=&quot;redditold-11473&quot;&gt;[https://old.reddit.com/r/CryptoCurrency/comments/a0nmkt/ethereums_central_point_of_failure_no_one_is/ ETHEREUM’S CENTRAL POINT OF FAILURE NO ONE IS TALKING ABOUT : CryptoCurrency] (Oct 13, 2022)&lt;/ref&gt;<br /> <br /> &lt;ref name=&quot;redditold-11474&quot;&gt;[https://old.reddit.com/r/egem/comments/a0retr/ethereums_central_point_of_failure_no_one_is/ ETHEREUM’S CENTRAL POINT OF FAILURE NO ONE IS TALKING ABOUT : egem] (Aug 18, 2023)&lt;/ref&gt;<br /> <br /> &lt;ref name=&quot;redditold-11475&quot;&gt;[https://old.reddit.com/r/CryptoCurrency/comments/a1v92j/do_not_download_ethereum_classic_geth_intruder/ Do not download Ethereum Classic geth, intruder has control of ETC's Github. : CryptoCurrency] (Aug 18, 2023)&lt;/ref&gt;&lt;/references&gt;</div>

Azoundria