
Exploit Dev, Security Researcher, Hobby Quant, Solving Problems Ex ctf @FluxFingers, @allesctf, @Sauercl0ud Affiliated @the_secret_club
Singapore
Joined January 2019
- Tweets634
- Following370
- Followers925
- Likes563
OAI training new model i suppose or something cause performance is super degrading. Tempted to swap to claude in the meantime but then i got triggered to the moon after seeing "load-bearing" and "honest" appear after the first prompt so i.g I gotta write some code by hand now
1
3
269
Hes right, but where is the new abstraction layer. It's not going to be the "You are right to push back on that" chat window
“Why would I look at code? It’s like assembly, like a compiled artifact.”
Sensei @karpathy fully agentic, 18m after “I don’t really use autocomplete AI code tools”
1
333
These guys are doing a huge service to humanity.
On July 25, our team hacked OpenAI.
It took us less than 72 hours.
Two vulnerabilities chained together gave us access to ChatGPT and Codex accounts belonging to OpenAI employees. We demonstrated the impact with a harmless PR in OpenAI’s internal monorepo.
The full chain:
HEIF upload → libheif heap overflow → RCE → OpenAI SSO flaw → ChatGPT/Codex takeover → connected GitHub → internal PR.
OpenAI fixed the SSO issue roughly 14 hours after our report.
Research by @rootxharsh, @S1r1u5_ and @iamnoooob.
Full technical write-up:
hacktron.ai/blog/hacking-ope…
brymko retweeted
On July 25, our team hacked OpenAI.
It took us less than 72 hours.
Two vulnerabilities chained together gave us access to ChatGPT and Codex accounts belonging to OpenAI employees. We demonstrated the impact with a harmless PR in OpenAI’s internal monorepo.
The full chain:
HEIF upload → libheif heap overflow → RCE → OpenAI SSO flaw → ChatGPT/Codex takeover → connected GitHub → internal PR.
OpenAI fixed the SSO issue roughly 14 hours after our report.
Research by @rootxharsh, @S1r1u5_ and @iamnoooob.
Full technical write-up:
hacktron.ai/blog/hacking-ope…
Got targeted by a "semi" sophisticated phishing/scam attempt just now.
Step 1) Receive an official email from google that my email was used as a recovery email for [email protected] (first image).
Step 2) (optional im not sure) Click on remove email. Appeard to be already removed.
Step 3) Receive call from SG registered number 3106 2518 (all previous attempts have been from foreign numbers).
Step 4) Matthew from "google" is very professional in following a well thought out script that might come straight out of a real support playbook.
Step 5) Matthew sends whatever that email is. (second image) The link in question points to the official hotelprices support page on support(.)google(.)com
Headers:
from:[email protected]
reply-to:[email protected]
to:[email protected]
< At this point I kind of got excited and tried to record, but my nontechnical ass didn't know that the iphone call recording will tell the other side and Matthew hung up >
My guess is that given the link doesn't work, the fake support agent would tell me to type in a custom url or something.
1
12
743
nice bug in csgo mate
OOB reads in network message handlers leads to RCE VALVE Bug Bounty PoC $7500 Bounty
Follow us: youtube.com/@NullSecurityX
#BugBounty #CyberSecurity
1
4
787
Yeah its gonna be great, trust.
Introducing Claude Code Security, now in limited research preview.
It scans codebases for vulnerabilities and suggests targeted software patches for human review, allowing teams to find and fix issues that traditional tools often miss.
Learn more: anthropic.com/news/claude-co…
1
739













