NUΞ (@chainNue) header
NUΞ (@chainNue) profile picture
Joined July 2022
Everything I learned about Prompt Injection Attacks in last 2 years is here in this guide. This should be your stepping stone to the field of AI Red Teaming. Link in comments 👇
10
123
5
606
41,398
BREAKING: $100,000 #Bitcoin
989
5,952
996
30,010
1,700,400
Confirmed, in my initial three contests on @HatsFinance, I secured 1st position in Paladin, 2nd in BFX, and also 2nd in Origami.
6
2
10
1,192
Look forward to further participation in @HatsFinance, which I currently regard as the most transparent platform for auditing.
1
2
176
Featuring on-chain and transparent submissions, immediate feedback from the protocol developer who also serves as the adjudicator, non-diluted payouts ensuring predictable outcomes, and swift payout timelines.
2
171
Keep your eyes open for anything, you never know when your luck knock on your door
151
thought experiment: how do you responsibly disclose a bug in a smart contract that was either a) deployed anonymously and has no known/reachable devs b) deployed non-anonymously but is immutable and the devs have explicitly stepped back to maintain an arm's length relationship
44
19
6
178
77,135
Failed two escalations in a row. Definitely need to consider my time management when trying to commit in an open audit contest
103
People are saying all kinds of terrible things while being uninformed so allow me to share more details. I've initiated coordination privately with Immunefi officials 3 hours before the white-hack. 90 minutes later, I realized the asset is currently used by the frontend and although the contract is not in scope (which almost certainly means a zero-ish bounty), fully disclosed it to Sushi with a mainnet fork POC. About 30 minutes later Sushi replied saying they are actively working on it. Unfortunately, Immunefi system only sent a mail saying the issue is escalated (automated msg), and not that there's a new message, due to throttling. The script locating wallets at risk finished and showed 0xsifu has the vast majority of funds at risk. It was ~5:30 AM local time and I saw an option to save most funds. There was incomplete information - I couldn't know if the team would reply before the start of next week. You can't know when an attacker would strike and steal all funds. MEV was a possibility, but didn't imagine it would be this fast and deadly (attack required a callback and had 2 setup transactions). I had a ledger setup so going private mempool would take a long time. I decided to white-hack 100 ETH (to verify I'm not bricking most funds) followed by the rest of 0xsifu and other significant wallets. 99.99% of people have never put themselves in such high-pressure situations and don't know what it's like. I've also factored in that the contract can't be paused and you can't coordinate everyone's revokes, so white-hack is the only real play even for the team. In hindsight, it was a mistake. But we're all biased with the results in a specific universe where the MEV unknown was worst-case, the team was actually aware, and we don't get a chance to see an attacker taking it all without the white-hack. Everyone who knows me is aware of the countless millions of $ I've saved in the ecosystem, my ethics, integrity, transparency, and never-ending support and education for new auditors. Seeing some allegations and people bashing me without context is heartbreaking. The only thing keeping me from sinking is support from dear community members and friends. Let's take the opportunity to improve as a community and formulate clear policies for when white-hacking is the right thing to do (it's usually not) and the exact procedure. Regarding the 10ETH bounty 0xsifu chose to award me, which seemed to annoy some folks, I'm donating it to the recovery fund. If my intention was to monetize from this hack there were a billion better ways. I'm here for the crypto users and will continue to ethically safeguard them for years to come.
75
65
37
680
159,690
BREAKING: Circle $USDC stablecoin falls under $0.90
828
1,848
587
9,206
2,266,901
1/12 [Interim Update of User Swap Incident] At 4am UTC, our team was alerted to a trade that encountered an unusually low return on the user’s swap. xitter.cf/spreekaway/status/1634… Our team is working hard to resolve this unfortunate matter. Summarized details below ⬇️
Ok I think this may be taking it too far
92
224
138
691
772,440
That's why, in competitive audit contest, it's kind of low benefit to use it, as many are doing it (even the protocol dev before asking to be audited)
🧰 All your smart contract security tools are shit ...Or at least, according to a recent research study After analyzing 516 bugs across 2021-2022, they discovered: - How good our tools are - How to categorize web3 bugs - How to use this knowledge to win $102k in audit contests
55
Since the @optimismFND contest rewards were announced, a bunch of people have asked me about the logistics of working with @trust__90. How did we share information? How did we support each other? I've experimented with this a lot so figured it might be useful to share publicly.
18
42
13
252
38,330
hack first negotiate later #HFNL
38
🚨🚨 How to get 10x better responses with this secret ChatGPT Prompt Hack 🚨🚨 ✅ It will guarantee to give you better answers in ChatGPT 🧙🏻‍♂️ Follow these 7 steps: 🧵 Thread, Let's dive in
87
397
47
1,980
271,514
Reentrancy alone led to $81.2M stolen in 2022!! How are there still so many basic exploits in the wild? Lack of talent? Negligent protocols? Both? @blockthreat @DefiyieldSec
2
8
2
23
2,146
One of the hardest things for new auditors is getting your head around a code base. I remember feeling like I was aimlessly jumping in circles. Based on the DMs I've been getting, seems like this is a common experience. Here's the process I now use for every audit...
30
143
11
587
105,650
A small group of really smart people are already working in 2030. They will own the future. Here are 28 terms that get you up to speed (starting today):
179
1,524
107
6,329
2,029,819