←
Pi3cH727 posts
Pi3cH avatar

Pi3cH

@pi3ch

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

◷ Joined August 2010▧ 77 Photos and videos
SecDim avatar
⟳ Pi3cH retweeted
SecDim@secdim·Nov 11

MCP challenges now on SecDim Play, mapped to the OWASP MCP Top 10:2025. Each is an MCP server or AI agent with a security vulnerability: find and fix it. Link in the reply.

Post attachment
Pi3cH avatar
Pi3cH@pi3ch·Nov 4

Your app is vulnerable to SQL injection even with ORM or parametrised query. See how this edge case works and how to protect against it. play.secdim.com/game/javascr…

In Node.js's mysql package, an object sent where a string was expected becomes part of the SQL by default, even when the query uses placeholders. This results into SQL injection. New JavaScript challenge:

Post attachment
Pi3cH avatar
Pi3cH@pi3ch·Oct 29

PHP2Shell Challenge #PHP2Shell #securecoding

New C++ challenge: Anushiya.cpp. One process handles requests one after another, and each request's memory should leave no trace. Find the vulnerabilities in the cleanup and fix them. Built from PHP2Shell (CVE-2026-109618, CVE-2026-109619).

Post attachment
Pi3cH avatar
Pi3cH@pi3ch·Oct 6

"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

Post attachmentPost attachment
Pi3cH avatar
Pi3cH@pi3ch·Oct 1

⚠️ 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:

Post attachment
Pi3cH avatar
Pi3cH@pi3ch·Sep 7

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.

Pi3cH avatar
Pi3cH@pi3ch·Sep 5

RSA-260 cracked

4397328654844826923795068102505872571721883526553349659561256924505973939597593482272505698004801207988043088656411102133523080581 divides RSA-260

Pi3cH avatar
Pi3cH@pi3ch·Aug 27

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

Post attachmentPost attachmentPost attachment
Pi3cH avatar
Pi3cH@pi3ch·Aug 26

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.

Post attachment
SecDim avatar
⟳ Pi3cH retweeted
SecDim@secdim·Aug 25

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

Post attachment
Pi3cH avatar
Pi3cH@pi3ch·Aug 21

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

Pi3cH@pi3chJul 23

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

Post attachment