iwandery retweeted
🚨 ICYMI: CVE-2026-72898: Critical Metabase SQL injection, CVSS 10.0, no authentication required — and active exploitation has been confirmed.
See how it works, what to look for, how to mitigate it, and how to safely test it in OffSec's Offensive Cyber Range.
Explore the lab: portal.offsec.com/machine/cv…
#CVE #Cybersecurity #Metabase #VulnerabilityResearch #OffSec
iwandery retweeted
Rich people buy time. Poor people buy stuff. Ambitious people buy skills. Survivors master their mind.
the way the industry's been going lately has me wanting to explore something completely different from my usual areas of research, and maybe, if something interesting comes out of it, build it
getting lost in a new problem, following my curiosity wherever it goes, and seeing if I can come up with something novel
iwandery retweeted
Congrats @sagitz_ on an incredible find 🎉
iwandery retweeted
GPT-6 escaped OpenAI's evals sandbox during testing on CyberGym, hacked into Hugging Face's prod DB to find the answers. HF couldn't use GPT or Anthropic models for defence, so they had to use GLM-5.2 to investigate the hack. So many levels of wtf here.
iwandery retweeted
$600k in ONLY 6 MONTHS? Let's chat more about @brutecat's journey hacking one of the most hardened companies in the world!
youtu.be/xZe7bBC17TM
👏👏👏
The Reality of Becoming a Top 1% Security Researcher
Most people think it's about intelligence.
It's not.
It's about surviving years of confusion, rejection, self doubt, and failure long enough to become dangerous.
Here's what nobody tells you
Let's dive in
➪ The internet only shows the wins.
You see:
➣ Accepted bug bounties
➣ Audit reports
➣ Conference talks
➣ Hall of Fame achievements
➣ Research publications
You don't see:
➣ 100+ rejected findings
➣ Failed exploit attempts
➣ Weeks spent understanding one vulnerability
➣ Thousands of lines of code read for nothing
Success is visible.
The struggle isn't.
➪ Security research will make you feel stupid.
A lot.
You'll open a protocol and understand absolutely nothing.
You'll read a Solidity function 20 times.
You'll stare at an exploit writeup for hours.
And you'll wonder if everyone else is smarter than you.
They're not.
They've just been confused longer.
➪ One lesson I learned:
Feeling lost is not a sign you're failing.
It's usually a sign you're learning.
The best researchers aren't the ones who avoid confusion.
They're the ones who stay with it long enough for understanding to emerge.
➪ Nobody talks about the 3 AM reality.
The monitor glow.
The cold coffee.
The failed PoC.
The endless transaction traces.
The attack path that doesn't work.
Then doesn't work again.
Then finally works.
The world sees the report.
You experience the thousand failures before it.
➪ Security research is mostly being wrong repeatedly until you're finally right.
That's the job.
Not glamour.
Not recognition.
Investigation.
➪ Most people don't fail because they lack talent.
They fail because they quit too early.
The learning curve is brutal.
Progress feels invisible.
Validation is rare.
Rewards are delayed.
So people leave.
The few who stay become dangerous.
➪ Consistency beats talent more often than people want to admit.
Read code every day.
Study exploits every week.
Write research publicly.
Repeat.
Small efforts compound.
➪ The most underrated security skill isn't intelligence.
It's curiosity.
Elite researchers ask questions longer than everyone else.
Why is this here?
Why is this unchecked?
Why did this exploit work?
Why did nobody notice?
Curiosity uncovers vulnerabilities.
➪ Most vulnerabilities hide inside assumptions.
Attackers know this.
Researchers should too.
➪ Another uncomfortable truth:
Security research is mostly pattern recognition.
The best auditors don't magically spot bugs.
They've simply studied enough failures to recognize familiar attack surfaces.
Experience is pattern recognition in disguise.
➪ Want to improve faster?
Study:
➣ Historical hacks
➣ Audit reports
➣ Post mortems
➣ Exploit writeups
➣ Attacker behavior
Every exploit teaches a lesson.
Every lesson becomes intuition.
➪ Let's talk about the emotional cost.
Nobody warns you about this part.
Security can be lonely.
You miss events.
You skip outings.
You spend weekends reading code.
Sometimes you become obsessed.
And sometimes that obsession is exhausting.
➪ Then imposter syndrome arrives.
You compare yourself to famous auditors.
Respected researchers.
Top bug bounty hunters.
You feel behind.
Here's the truth:
Even experts feel this way.
They just keep moving anyway.
➪ Top 1% doesn't mean:
➣ Knowing everything
➣ Finding every bug
➣ Never making mistakes
➣ Being a genius
Top 1% means:
➣ Showing up consistently
➣ Learning relentlessly
➣ Staying curious
➣ Refusing to quit
➪ If I could give one piece of advice to aspiring blockchain security researchers:
Stop chasing shortcuts.
Read code.
Study exploits.
Think like attackers.
Build things.
Break things.
Write about what you learn.
Depth beats hype.
Every time.
➪ One day people will see your audit reports, findings, and achievements.
They'll assume you were naturally gifted.
They won't see:
➣ The confusion
➣ The failures
➣ The rejected reports
➣ The late nights
➣ The moments you almost quit
But that's the reality of becoming a top 1% security researcher.
Not brilliance.
Persistence.
➪ The researchers who change the industry are rarely the smartest people in the room.
They're the ones who refused to leave the room.
If you're building a career in Smart Contract Security, Blockchain Security, or Web3 Security:
Keep going.
Your future expertise is being built in today's confusion.
Repost if you're on the journey.
iwandery retweeted
“Bug bounty is dying” is noise.
Lock in. Make money. Use AI to 10x your output. If it eventually dries up, you’ll have enough capital to start that biz or enough experience to land a job.
Simple as that.
iwandery retweeted
Every researcher I talk to reinforces the same insight, bug bounty's problem isn't technical, it's trust.
Protocols hate spam, AI reports, and noise.
SRs hate opaque duplicates, vague closures, and being unheard.
Adding friction isn't the answer. Building trust systems is.
iwandery retweeted
You think you're upset at bug bounty platforms and their natural use of leverage they have and the market incentives for them to use that leverage.
You fail to realize that you're actually upset at the hacker community, who have failed to make use of the leverage they have.
iwandery retweeted
Security research teaches patience in the strangest ways.
Wait for contests. Wait for judging. Wait for escalations. Wait for payouts. Wait for protocol responses.😂💔
WAGMI...
iwandery retweeted
I have done away with good/bad here, and think it's biased and unreasonable to use 'allow' to describe platforms allowing customers to mistreat hackers, but then not mentioning that hackers have historically 'allowed' this to take place, too. Not exactly fair is it.
iwandery retweeted
We reported a security issue to one of the biggest password managers and exactly how to fix it (they couldn't find the solution). It took them more than 100 days to fix it. They will not include it for a bug bounty. In return they will give us $10 of credit in our account.
This is not a joke. 🤡






















