(Cyber) security Researcher. Serial Founder (@secdim|@sectalks|@elttam). Senior Lecturer (@unsw).

Zfkulf, Hbzayhsph
Joined August 2010
"AI is telling me there's an RCE vulnerability here, but how do I validate it?" This was one of the most common questions from participants at @secdim Vibe Coding Security workshop at @NDC_Conferences Oslo. The reality is that AI helps, but we are the gatekeepers. We make the call on the security of our software. Using some techniques, we can guide AI to find security weaknesses. Assurance can only come from us. A skilled developer knows insecure design patterns, understands AI blind spots, and has the hands-on skill to verify vulnerabilities. That last point was the key takeaway for participants. We ran the workshop in Oslo. The next one is in London on 25-26 January 2027 (seats are limited. link in the comments). #security #vibecoding #workshop
1
1
50
⚠️ A zero day security advisory by @secdim security research team in an official JWT library for Python. #cve #0day
We found CVE-2026-102274 in PyJWT: one malformed RSA key could stop an entire JWK Set from loading. Fixed in 2.14.0. Technical writeup:
1
2
156
Wondering why there are many MCP vulns? Per MCP official spec, Authorization is OPTIONAL. Even for HTTP protocol is a SHOULD not a MUST. Now good luck pushing for OAuth 2: modelcontextprotocol.io/spec…
1
53
The next wave of hacker are technical writers: The better you are in English, the better hacker you are. From Prompt injection to MCP and A2A injections, your exploit strength depends on your English proficiency.
1
1
1,760
RSA-260 cracked
4397328654844826923795068102505872571721883526553349659561256924505973939597593482272505698004801207988043088656411102133523080581 divides RSA-260
1
212
Half the "zero-days" on my feed this week would fall apart if anyone checked Apache's own repo first. This one did. Real insecure pattern, wrong severity claim.
Researcher called this an unpatched Log4j RCE. Apache documented the same path in July as hardening, not a vuln. Report pulled, account deleted, no CVE. Root cause: MarshalledObject is allowlisted but its payload byte array is never inspected. Free challenge. link in comments
1
79
AI Shifted the Skill. It Didn't Remove It.
Has AI killed secure code training? No. It made it critical. → AI writes 42% of committed code → Security findings up 10x in 6 months → Iterative AI fixes make vulns worse, not better The skill that matters now is catching what AI gets wrong. Link in comments.
63
Pi3cH retweeted
Black Hat USA 2026 is done. SecDim AI Attack & Defence Wargame ran for two and half days. 🥇 1st Grigorii Liullin 🥈 2nd Nicholas Hinojosa 🥉 3rd Isauro Zaragoza Congrats. You out-patched everyone in the room. Get notified for the next one. Link below. #blackhat
1
1
3
133
4Cs of Cloud Native Security: Cloud, Clusters, Containers, Code. Now a 5th ring: AI Code. AI-generated code doesn't add a new risk next to Code. It stacks on top of it. Nobody reviews it fully. Authorship unclear. Intent unclear. The dev "driving" often can't explain what it does. Complexity compounds. Learn more at my presentation at @PyConAU
I always enjoy speaking at grassroots tech conferences, and this time here in Australia @PyConAU 🇦🇺. There is a misunderstanding among some that "AI has solved most of software security problem"! Rather than arguing with this opinion, in this talk, based on real data, I will show that this is wishful thinking, and where the root causes of software security vulnerabilities really are. Join me Friday. Ballroom 3, 10:45am. First cybersecurity talk of the conference. Also -> Voucher code for 10% off in comments. #appsec #securecoding #aisecurity #devsecops
1
152
Build an AppSec challenge for the SecDim @AppSec_Village Wargame at @defcon 34 and win a Flipper Zero + Video Game Module Challenge submissions close on 31 July, Only one week left! 👉 appsecvillage.com/ctf #appsec #securecoding #defcon #ctf
125
Submit challenge to win prizes! Deadline 31st July. @defcon @AppSec_Village
Build an AppSec challenge for the SecDim @AppSec_Village Wargame at @defcon 34 and win a Flipper Zero + Video Game Module Challenge submissions close on 31 July, Only one week left! 👉 appsecvillage.com/ctf #appsec #securecoding #defcon #ctf
1
113
I always enjoy speaking at grassroots tech conferences, and this time here in Australia @PyConAU 🇦🇺. There is a misunderstanding among some that "AI has solved most of software security problem"! Rather than arguing with this opinion, in this talk, based on real data, I will show that this is wishful thinking, and where the root causes of software security vulnerabilities really are. Join me Friday. Ballroom 3, 10:45am. First cybersecurity talk of the conference. Also -> Voucher code for 10% off in comments. #appsec #securecoding #aisecurity #devsecops
1
2
2
400
A great research article by Mahyar, our intern at @secdim showing the realities of some libraries.
“it parses” does not mean “it is secure”. Many libraries prioritise ease of use or safety by omission rather than offering fine-grained security controls. 👉 Full write up: secdim.com/blog/post/the-mis… #appsec #securecoding #javascript #programming
126
Feedback loop security degradation: the more you run AI to "fix security", the worse the outcome will be after each iteration. This is interesting academic research. ~40% increase in critical vulnerabilities after just five iterations. Security-focused prompts still introduced new flaws — cryptographic implementation errors above everything else. Explicitly asking the model to "fix security" made things worse. The code looked more sophisticated each round. That's the trap. Developers trusted the output, reviewed less, and missed the flaws the model introduced. At @secdim , we see this also. Developers skip review because it is "too much to review". Those who do review miss the security flaws. The skill to critically evaluate AI-generated code is degrading. The research recommends mandatory human security code review and no more than three (3) consecutive LLM iterations. Paper in comments. #aisecurity #appsec
1
89
As expected, 2026 is flooding us with CVEs, but exploitation stays rare. Lots of noise. H1 2026: 35,364 new CVEs (more than any full year pre-2024). One every 7.4 minutes — up 49.5% from H1 2025. Only 85 (0.24%) on CISA KEV so far. Vulns come faster than ever, but confirmed exploitation is low. The real challenge isn’t patch volume — it’s signal-to-noise. Follow the great work by jerrygamblin.com/2026/07/01/… #cve
77