00xWizard (@00xWizard) header
00xWizard (@00xWizard) profile picture

Web3 Security Researcher | I help teams avoid being on https://teapaw.org/t.co/yWfcdmc0iW | DM for audits

Joined May 2022
Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)Photo by 00xWizard (@00xWizard)
Smart choice by @flow_blockchain A rollback wouldn't have had any effect on the hacker, hope they can recover fast. Laying out the recovery plan was a smart choice.
Replying to @flow_blockchain
UPDATE: ISOLATED RECOVERY PLAN Flow Foundation has developed a revised remediation plan working with ecosystem partners. This approach was developed following direct consultation with bridge operators, exchanges, and infrastructure partners. WHAT THIS MEANS → No network rollback / reorg → No transaction replay required by partners → Legitimate user activity preserved → Over 99.9% of accounts unaffected and fully operational at relaunch HOW IT WORKS At network restart, accounts identified as recipients of fraudulently minted tokens will be temporarily restricted as a precautionary measure. The Flow Foundation is working with independent blockchain forensic firms to verify the precise token types and quantities attributable to the exploit. Flow core developer team will propose a software upgrade to node operators. This software upgrade will temporarily enable the Community Governance Council to remediate fraudulent assets. This requires opt-in adoption by independent node operators; no single entity can act unilaterally. Once validators reach consensus: • Accounts affected by the attacker’s distribution attack will be temporarily restricted • Affected accounts identified and verified through independent forensic analysis • Fraudulent tokens will be destroyed via transparent, auditable on-chain transactions • Each remediated account will be immediately restored to full access • Upon completion, a subsequent upgrade will revoke all elevated permissions PHASED RESTORATION Phase 1: Cadence environment live, EVM temporarily restricted (read-only) Phase 2: Cadence remediation (~24-48 hrs) Phase 3: EVM remediated and re-enabled Phase 4: Bridges/exchanges resume at operator discretion following verified stability Technical implementation details: docs.google.com/document/d/1… Next update at 9pm PT
1
5
195
OG labs X account @0G_labs was hacked by an ex-community member, he states that the team scammed the community and this is a payback in a way
3
1
25
4,778
Whatsapp just proves to be fragile like usual. It would be better to delete it for now
WhatsApp 0-Click Vulnerability Exploited Using Malicious DNG File! The exploit, demonstrated in a proof-of-concept (PoC) shared by the DarkNavyOrg researchers, is initiated by sending a specially crafted malicious (DNG) image file to a victim’s WhatsApp account. As a “zero-click” attack, the vulnerability is triggered automatically upon receipt of the malicious message, making it particularly dangerous as victims have no opportunity to prevent the compromise.
1
2
193
Unfortunately @nemoprotocol on @SuiNetwork has been hacked for 2M+ The stolen funds have been bridged from Arbitrum to Ethereum
1
1
94
ok so there is another fake one from Hardhat; please always triple check the extensions you install: - https://open-vsx[.]org/extension/NomicFdn/hardhat-solidity (do not touch!) the namespace was claimed here: github.com/EclipseFdn/open-v…, the legit extension was downvoted at the same time they released the other fake one. From a quick glance it's exactly the same approach as documented earlier for the other solidity extension.
so the malicious part is in the `modal.js` file; TL;DR is the following. The obfuscation applied is: - `hexColors` array holds Base64 fragments padded with `#` - Reversed, joined, stripped of `#`, Base64-decoded - Decoded code executed via hidden `eval` (`ZXZhbA==`) The behaviour is: - Targets Windows (`win32`) and macOS (`darwin`) only - Disables `TLS` certificate verification (`NODE_TLS_REJECT_UNAUTHORIZED = "0"`). - Fetches remote JS from: Windows → p92nd[.]pages[.]dev/cj292ke.txt macOS → p92nd[.]pages[.]dev/ufjm20r.txt - Executes fetched code via `eval` (arbitrary code execution) - Uses `process.exit(0)` for stealth termination on errors or empty payload I won't got into more details for now. Actions are taken.
8
29
12
118
35,136
We are about to see a massive surge in AI related hacks, where an agent accesses something it wasn’t supposed to.
34
27
4
295
12,351
If you are a Solidity dev or a Junior-Mid auditor, make sure you pay attention here.✍️ Must-know contracts: Token contracts: The most used token standards are EIP20 for fungible tokens, and EIP721 for NFTs. Proxies: There are many different proxy implementations, have a look at the OpenZeppelin Upgradable Proxies. MasterChef contract: A staking contract by SushiSwap where users deposit LP tokens and receive rewards. Compound: A must-know protocol if you want to have solid knowledge of Lending/Borrowing codebases. UniswapV2: The basis for understanding automated market makers (AMMs) in general. You should also understand how LP tokens work.
2
13
2
116
7,273
Replying to @00xWizard
I mean people get lost in resources. It's hard to stick to the right path if everyone tells you different things that you should do
1
1
4
1,048
Understanding Smart Contract Metadata! When solidity generates the bytecode for the smart contract to be deployed, it appends metadata about the compilation at the end of the bytecode. We will examine the data contained in this bytecode. rareskills.io/post/solidity-…
24
1
112
6,838
Fight for privacy. Privacy is good. Privacy is normal.
16
41
5
260
17,043
We are BEYOND thrilled to be announcing the next generation of web3 security: Introducing: @codehawks The Smart Contract Audit Marketplace. 🦅 What is CodeHawks, and why did we decide to build this 👇
16
75
6
453
63,988
KnowledgeLists 🗒️ Ethereum Smart Contracts Security Recommendations and Best Practices: l’d appreciate a retweet, spread the knowledge 😈 github.com/guylando/Knowledg…
2
38
1
108
10,694
I could never fully understand the EVM until I stumbled across this video. This is the holy grail of EVM alpha. 🏆 Everything you need to know, laid out step by step. youtube.com/watch?v=RxL_1AfV…
13
40
2
227
21,185
List of 100+ DEFI Attacks + Hacks Analysis 🕵️‍♀️ Must be Read!!! Together for safer Web3 🤝 I’d appreciate a retweet, spread the knowledge 👊 wooded-meter-1d8.notion.site…
2
58
1
172
11,224
00xWizard retweeted
If you are someone who is starting in the auditing world (for example doing the @RealJohnnyTime course), you might be wondering how to classify your findings. When are they highs? When lows? Today, I have a quick guide for you 🧵👇
2
7
2
20
2,664
The old narrative: ❌ Does the project have an audit? Isn't good enough. We need to ask at least these questions: ✅ Audited? ✅ Stateless and Stateful Fuzz Tests? ✅ Invariants Understood? ✅ Documentation? ✅ Static analysis passed? Optional: - Formally Verified?
26
23
3
253
22,107
Auditor tip 💡 The vulnerability arises from the fact that as per EIP-712 - strings, as dynamic types, should be encoded as a `keccak256` hash of their values, yet this function version fails to do so.
8
25
2
160
23,818
Foundry tip: Struggle no more with random addresses for testing! "makeAddr" is a game changer! - Labels the address so it looks sexy in stack traces - Turns the name into a pk by doing pkey == keccak(str) and label + returns vm.addr(pkey) so you can sign messages
6
24
2
199
15,674
00xWizard retweeted
I have recently read this great article on "what happens when you send 1 DAI". Even though it might take you ~1hr to read it, it's worth it. It shows off the beauty of the Ethereum nodes & EVM technology and its great property - open source. A must read✌️ notonlyowner.com/learn/what-…
22
118
14
459
72,274