kodosec's profile picture. Posting about Web2, Web3 and AI security

KodoSec

@kodosec

Posting about Web2, Web3 and AI security

Effective Web3 security goes beyond just smart contracts. Let's remember the importance of securing frontends, APIs, and dependencies. A holistic approach protects users from threats like phishing & drainers at every layer. #DeFiSecurity #FullStackSecurity


Honestly, seed phrases have got to go. Expecting average users to manage 12/24 words securely is Web3's biggest delusion. We need Passkeys & embedded wallets yesterday. Security shouldn't require perfect opsec from everyone. #Web3Security #DeFiSecurity


What’s the biggest Web3 security risk?


KodoSec reposted

Nvidia has increased compute 125x faster than Moore's Law for the past 8 years.. @PeterDiamandis at @Abundance360 Conference today.

Bill_Gross's tweet image. Nvidia has increased compute 125x faster than Moore's Law for the past 8 years..

@PeterDiamandis at @Abundance360 Conference today.

What's the most valuable lesson you've learned about smart contract security?


Simplicity is king in smart contract security. Complex code is harder to audit and more prone to errors. #KeepItSimple #Web3Security #SmartContracts


Auditing a Web3 project isn't just about finding bugs in the code. It's about understanding the entire system, the business logic and the potential economic attack vectors. #Web3Security #SmartContractAudit #Auditing


⚠️Have you seen this common Solidity vulnerability? delegatecall executes code in the context of the caller, potentially overwriting your storage! address lib; fallback() external payable { (bool success,) = lib.delegatecall(msg.data); require(success);…


⚠️ Do you know this common Solidity vulnerability? Reentrancy attacks can drain funds from contracts if not handled carefully. Here's a vulnerable example: function withdraw(uint256 _amount) public { require(balances[msg.sender] >= _amount); (bool sent,) =…


🚩 Always verify function visibility in your smart contracts. Public versus external isn't trivial. Choosing incorrectly could: - Waste gas - Expose unexpected behaviors #SmartContractAudit #SolidityTips


Gas fees hurt, but bad code hurts more


Funds are SAFU

kodosec's tweet image. Funds are SAFU

KodoSec reposted

JUST IN: 🇰🇵 North Korea's Lazarus Group behind Bybit's $1.4 billion hack, ZachXBT reports.


Reentrancy attacks are still a thing in 2025—why do devs keep missing them? Seen it in 3 audits this year already


United States Trends

Loading...

Something went wrong.


Something went wrong.