BadgerDAO Malicious Code Injected: Revision history

10 May 2024

• curprev 16:0016:00, 10 May 2024‎ Azoundria talk contribs‎ 20,923 bytes +285‎ No edit summary

28 September 2023

• curprev 16:2116:21, 28 September 2023‎ Azoundria talk contribs‎ 20,638 bytes +1,852‎ Another 30 minutes complete. Additional sources merged in. Prevention completed. Information moved around. Tag: Visual edit

13 September 2023

• curprev 18:3318:33, 13 September 2023‎ Azoundria talk contribs‎ 18,786 bytes −207‎ Another 30 minutes complete. Additional sources merged in. Working on prevention. Information moved around. Tag: Visual edit

7 May 2023

• curprev 15:3315:33, 7 May 2023‎ Azoundria talk contribs‎ 18,993 bytes +534‎ No edit summary

28 February 2023

• curprev 11:4711:47, 28 February 2023‎ Azoundria talk contribs‎ 18,459 bytes +1,567‎ No edit summary

27 January 2023

• curprev 22:0622:06, 27 January 2023‎ Azoundria talk contribs‎ 16,892 bytes +16,892‎ Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/badgerdaomaliciouscodeinjected.php}} thumb|BadgerDAOBadgerDAO suffered a massive attack on their smart contract hot wallets. In this case, the vulnerability was not inherently in the contract, but they were tricked into adding an additional API connection, which allowed the attacker to inject malicious code. So far, the security of the smart contract has een improved and 40%..."