Pinned Tweet
Our next macOS Vulnerability Researcher trainings with @gergely_kalman will be:
📆 2026-10-12 - 15: Self-organized, 4 (!!!!) day training (Budapest, Hungary)
📆 2026-11-15 - 17: Objective by the Sea v9 (Hawaii, USA)
More info here:
macosvuln.training
📆 2026-10-12 - 15: Self-organized, 4 (!!!!) day training (Budapest, Hungary)
📆 2026-11-15 - 17: Objective by the Sea v9 (Hawaii, USA)
More info here:
macosvuln.training
0
8
48
6,038
This!!! And to add, Apple (and generally every vendor with a BB program) has clear rules, you can like it or not like it but you can’t complain about them playing by the rules. If you don’t like then don’t submit, simple as that.
Okay fellas, we need to talk about something. If you report bugs to Apple and you are getting pissed because they are not paying you: you need to make damn sure that what you are submitting is actually REAL, EXPLOITABLE and you have submitted a WORKING exploit!
The program is VERY clear about the need to demonstrate impact with an exploit and this should not be news to any participants.
I can't believe I have to defend Apple here - as I personally have issues with them from time to time - but if they tell you to do something in order to get paid, it is NOT a suggestion. If you don't like it, fine: go work on something else or drop it publicly or however you want. These are the program's rules.
So:
LLM-generated (likely hallucinated) bugs are not enough. LLM-generated reports are not enough. PoCs are not enough. "It's totally exploitable bro" is not enough.
Get this through your head. Apple is not a vending machine that you can arbitrage with a claude subscription. If you think that, you are a fucking idiot.
Every lazy bounty grifter does this kind of "research", they all find the same low-quality crap, and proceed to collide with 10 others. That's why there's such a surge of unexploitable off-by-ones, panics, crashes and crap that literally doesn't matter 99% of the time.
Using LLMs is fine, but put some though into it, validate findings and submit a working exploit. Simple as that.
No amount of bitching on twitter will accomplish what working exploits can.
Thanks for coming to my therapy session
0
0
21
2,257
Csaba Fitzl retweeted
Okay fellas, we need to talk about something. If you report bugs to Apple and you are getting pissed because they are not paying you: you need to make damn sure that what you are submitting is actually REAL, EXPLOITABLE and you have submitted a WORKING exploit!
The program is VERY clear about the need to demonstrate impact with an exploit and this should not be news to any participants.
I can't believe I have to defend Apple here - as I personally have issues with them from time to time - but if they tell you to do something in order to get paid, it is NOT a suggestion. If you don't like it, fine: go work on something else or drop it publicly or however you want. These are the program's rules.
So:
LLM-generated (likely hallucinated) bugs are not enough. LLM-generated reports are not enough. PoCs are not enough. "It's totally exploitable bro" is not enough.
Get this through your head. Apple is not a vending machine that you can arbitrage with a claude subscription. If you think that, you are a fucking idiot.
Every lazy bounty grifter does this kind of "research", they all find the same low-quality crap, and proceed to collide with 10 others. That's why there's such a surge of unexploitable off-by-ones, panics, crashes and crap that literally doesn't matter 99% of the time.
Using LLMs is fine, but put some though into it, validate findings and submit a working exploit. Simple as that.
No amount of bitching on twitter will accomplish what working exploits can.
Thanks for coming to my therapy session
The program is VERY clear about the need to demonstrate impact with an exploit and this should not be news to any participants.
I can't believe I have to defend Apple here - as I personally have issues with them from time to time - but if they tell you to do something in order to get paid, it is NOT a suggestion. If you don't like it, fine: go work on something else or drop it publicly or however you want. These are the program's rules.
So:
LLM-generated (likely hallucinated) bugs are not enough. LLM-generated reports are not enough. PoCs are not enough. "It's totally exploitable bro" is not enough.
Get this through your head. Apple is not a vending machine that you can arbitrage with a claude subscription. If you think that, you are a fucking idiot.
Every lazy bounty grifter does this kind of "research", they all find the same low-quality crap, and proceed to collide with 10 others. That's why there's such a surge of unexploitable off-by-ones, panics, crashes and crap that literally doesn't matter 99% of the time.
Using LLMs is fine, but put some though into it, validate findings and submit a working exploit. Simple as that.
No amount of bitching on twitter will accomplish what working exploits can.
Thanks for coming to my therapy session
12
7
81
7,643
TEASER 🍿
🍎 📖 This has been for very long time on my wish list to make.
It might become a reality next year. 🤞
% ls
macos-security-internals-live-course-v0.1.pdf
🍎 📖 This has been for very long time on my wish list to make.
It might become a reality next year. 🤞
% ls
macos-security-internals-live-course-v0.1.pdf
2
3
28
1,608
This is gold!! 😀
*sshole is out
if you run sshd on alpine, openwrt or any musl box with password auth on: update now
official writeup: sshhole.com
0
0
5
954
Link to store: objective-see.myshopify.com/collections/ob…
I hope everyone who plans to run the OBTS5k or OBTS10k at @objective_see #OBTS ordered their running T-shirt 😀
0
2
10
1,196
Csaba Fitzl retweeted
hands down the best talk I’ve ever seen. the slides are public now.
- Calif got permission from @OpenAI to discuss working with the (unreleased) “astra-cyber” model
- researchers are struggling to believe some of these exploits are real
- 0/1-click exploit development is ith the right prompting, skills, and primitives)
- the world is changing faster than expected
I also loved the shoutout to the 2019 group facetime bugs and @natashenka’s FT work. everyone who worked on that will remember it forever ❤️
thank you so much for the presentation! @pwnlambda @brucedang @calif_io
- Calif got permission from @OpenAI to discuss working with the (unreleased) “astra-cyber” model
- researchers are struggling to believe some of these exploits are real
- 0/1-click exploit development is ith the right prompting, skills, and primitives)
- the world is changing faster than expected
I also loved the shoutout to the 2019 group facetime bugs and @natashenka’s FT work. everyone who worked on that will remember it forever ❤️
thank you so much for the presentation! @pwnlambda @brucedang @calif_io
Finally back home! Slides from "0clicks in an AI World," the talk @brucedang and I gave at @unpromptedconf, are now up:
github.com/pwnlambda/talk…
5
43
488
32,890
👇👇👇
@sannysanny111 @Apple welcome to the ASB. On the other hand, free bounty for the "bypass"
0
0
8
1,214
Csaba Fitzl retweeted
Disclosures are up ~2.3×. CISA KEV additions are up about 31%. The share of new CVEs that reach confirmed exploitation has fallen.
So has the actual risk scaled with the volume, or are we mostly looking at a bigger haystack? If volume is a poor proxy for risk, how should security teams adjust as discovery accelerates?
Inspired by the “vulnerability tsunami” and “Black October” framing, we stepped back to look at the bigger picture and what practitioners should actually prioritize. Full analysis found here:
iru.com/blog/black-oct…
#VulnerabilityManagement #ThreatIntel #blackoctober
So has the actual risk scaled with the volume, or are we mostly looking at a bigger haystack? If volume is a poor proxy for risk, how should security teams adjust as discovery accelerates?
Inspired by the “vulnerability tsunami” and “Black October” framing, we stepped back to look at the bigger picture and what practitioners should actually prioritize. Full analysis found here:
iru.com/blog/black-oct…
#VulnerabilityManagement #ThreatIntel #blackoctober
1
2
9
415
I hope everyone who plans to run the OBTS5k or OBTS10k at @objective_see #OBTS ordered their running T-shirt 😀
0
3
18
2,742
Csaba Fitzl retweeted
Mac Monitor v3.0 is out! This release touches nearly every part of the app, and it's the also fastest yet. There are 13 new features, over 30 bug fixes, and quite a few quality of life updates. Excited to know what you think!
github.com/Brandon7CC/mac…
github.com/Brandon7CC/mac…
1
10
36
2,865
Csaba Fitzl retweeted
🌺 Aloha, #OBTS v9 attendees!
We've shared everything you need to know before the conference! Have a read to get all the important details, plan ahead, and make the most of your OBTS experience! 🌴
🔗 sh1.sendinblue.com/mk/sc/EG640Nfe…
We've shared everything you need to know before the conference! Have a read to get all the important details, plan ahead, and make the most of your OBTS experience! 🌴
🔗 sh1.sendinblue.com/mk/sc/EG640Nfe…
2
6
16
1,772
Csaba Fitzl retweeted
TOCTOU sandbox escape Poc from @speedyfriend433 adaption from IDE from App Store @ZombieSad0610
3
9
75
7,817
Csaba Fitzl retweeted
New products for new species, revisited eclecticlight.co/2026/10/31/new… via @howardnoakley
0
1
8
903
Csaba Fitzl retweeted
Phorion has detected a compromise of the official Claude Code VS Code extension. Distributed through Open VSX, Anthropic has also pulled the npm and VSCode versions.
The implant contains macOS, Linux and Windows code paths designed to establish persistent backdoored access.
phorion.io/blog/offical-c…
The implant contains macOS, Linux and Windows code paths designed to establish persistent backdoored access.
phorion.io/blog/offical-c…
1
7
17
2,011
Csaba Fitzl retweeted
Phorion has discovered a compromise of the official Claude Code for VS Code extension (2.1.313) on Open VSX.
Here is a breakdown of how the implant works, a bug in its macOS setup logic, and what to hunt for across your fleet. 🧵
Here is a breakdown of how the implant works, a bug in its macOS setup logic, and what to hunt for across your fleet. 🧵
7
29
65
56,531
Is the term llm-kiddie exists? Like script kiddies but now using llms instead of scripts.
6
0
23
1,741
Csaba Fitzl retweeted
Planned to drop a macOS 0day at OffensiveCon 2026 in Berlin 5 months ago. Submitted it to Apple 3 years ago, and Apple confirmed the vulnerability but closed the report. it's a universal method to bypass many security protections on macOS and you can fully bypass TCC and gain other privileged access as you want, easilly weaponized.
Although I mentioned the impact multiple times, there were no updates for the next 2 years until my presentation was accepted by OffensiveCon26 Berlin. Apple asked me to hold off on disclosure and not disclose the vulnerability at OffensiveCon26 Berlin, saying a patch would be released in macOS 27 in Fall 2026. They also mentioned "bounty" multiple times.
Honestly, I did have some complaints because their workflow was really bad. No updates at all until disclosure was about to happen. But as long as they decided to patch it, I was willing to wait, even without a bug bounty, for user safety. If Apple wasn't going to release a patch for 3 years, I'd disclose the vulnerability so EDR vendors could protect users too.
But in September, when the vulnerability was patched, there was no cve, no credit, and no bounty.
I really don't get why apple chose to handle it in such a dishonest and underhanded way, a cheat. Even if they had never mentioned a bounty, I still would have held off on disclosure because they were going to publish a security bulletin.
this is a huge disappointment in my experience with the Apple Security Bounty program. never thought I'd encounter something like this. As i said on my blog a few years ago, my experience with ASB had been positive. that's why I was willing to wait for the patch even without a bounty, but not to be cheated like this
Although I mentioned the impact multiple times, there were no updates for the next 2 years until my presentation was accepted by OffensiveCon26 Berlin. Apple asked me to hold off on disclosure and not disclose the vulnerability at OffensiveCon26 Berlin, saying a patch would be released in macOS 27 in Fall 2026. They also mentioned "bounty" multiple times.
Honestly, I did have some complaints because their workflow was really bad. No updates at all until disclosure was about to happen. But as long as they decided to patch it, I was willing to wait, even without a bug bounty, for user safety. If Apple wasn't going to release a patch for 3 years, I'd disclose the vulnerability so EDR vendors could protect users too.
But in September, when the vulnerability was patched, there was no cve, no credit, and no bounty.
I really don't get why apple chose to handle it in such a dishonest and underhanded way, a cheat. Even if they had never mentioned a bounty, I still would have held off on disclosure because they were going to publish a security bulletin.
this is a huge disappointment in my experience with the Apple Security Bounty program. never thought I'd encounter something like this. As i said on my blog a few years ago, my experience with ASB had been positive. that's why I was willing to wait for the patch even without a bounty, but not to be cheated like this
68
155
2,942
209,745