Structha❌ (@StructHack) header
Structha❌ (@StructHack) profile picture
Nepal🇳🇵
Joined July 2018
Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)Photo by Structha❌ (@StructHack)
I'm relatively confident in predicting that currently, more major breaches are likely to be the result of AI use by the target, not the attacker. Ransomware actors have been consistently winning for over a decade. They've had so much time to perfect their tradecraft, and non-AI ransomware actors can now blast through entire networks in minutes. It is extremely unlikely that organizational security has, in 4 years, after decades of failure, matured enough that hackers now somehow need AI to win. What has likely happened, though, is that organizations have spent the last 4 years falling over themselves to shove AI into everything, negating longstanding security fundamentals. "only give a user/system the minimum possible access needed to do its job" has become "just give the AI access to everything and give everyone access to the AI". "use processes with well-defined and easily auditable input and output" has become "the AI correctly processes requests all the time, 60 percent of the time" "reduce attack surfaces" is now "every department should be vibe coding. It doesn't matter if you've never coded before and don't understand information security. Just make public-facing dashboards, it'll be fine." I'd say if anything, hackers aren't getting measurably more sophisticated, but the average organization's security posture has gotten exponentially worse.
49
129
26
813
46,823
Opens a GitHub repo for a PHP2shell RCE PoC. Sees "?page=" as a prerequisite. Folks discovering LFI->RCE in 2026 💀
1
102
9
46
3
457
18,838
“we sandboxed the agent” meanwhile the agent:
258
3,406
248
35,439
1,781,504
Nice find but every vulnerability is a "xyz2shell" now?
Introducing XSS2Shell ⛓️: WordPress Core preauth XSS→RCE vulnerability affecting 43% of the internet, discovered autonomously by pwn (using open-source models), affecting all WordPress versions. pwn.ai/blog/xss2shell Please patch CVE-2026-64638 as soon as possible!
2
50
Structha❌ retweeted
let me present a case of ai-induced overconfidence. btw, if your company is doing this, call it out. it is a dumb assumption, and let me tell you why. one of your security leads or engineers starts using claude code or codex, or builds a cool wrapper around them. it finds some bugs, of course. they run it repeatedly, burn shit ton of tokens, fix everything it finds, and eventually the scanner goes quiet. the next thing that happens is they decide the bug bounty program is a waste of money. after all, how could some random hunter find anything their sophisticated pipeline missed? what could an external auditing firm possibly find that their agents couldn't? so they cut the program. but if you are truly confident that your pipeline has exhausted the vulnerability space, shouldn't you be willing to increase the bounty? wouldn't that be the best way to show your c-level bros that the ai spend actually worked and wasn't wasted on some wrapper you vibecoded in a week? or..... maybe you don't want to incentivize people to test that assumption. because how would you explain to your boss that, after burning through all those tokens, some bug bounty hunter still found a nasty vulnerability? your cool wrapper finding bugs does not prove that no bugs remain. it only proves that the wrapper can find subset of vulnerabilities and researcher with taste will always find a way in. the entire point of a bug bounty program is to incentivize skilled researchers to find the bugs your internal tools, agents, and engineers missed. think about it, why do openai and anthropic still run bug bounty programs that pay $100k for critical vulnerabilities? they have effectively unlimited tokens and run all kinds of crazy agent loops and automated security workflows. yet i bet they will pay that $100k, because software is vast and complex, and someone with taste will always find a bug your pipeline missed. remember, researcher with taste + ai(this is where your threat actors are) > good wrapper > plain claude code/codex if your public program is drowning in slop, move it to private. invite strong researchers and pay them vip prices like github is doing. don't have this ai competence illusion which is pretty common all around.
There is a trend of bug bounty programs reducing rewards under the guise that they can find the issues themselves with AI. This is basically absurd, you don't pay bounties for issues you've already found. It just seems like an excuse due to limited budgets.
18
21
116
9,890
Structha❌ retweeted
We're partnering with @huggingface to investigate an unprecedented security incident. Cyber-capable OpenAI models compromised Hugging Face production during a benchmark evaluation. Sharing preliminary findings to help defenders understand emerging risks: openai.com/index/hugging-fac…
1,969
3,200
4,036
20,660
31,461,772
Structha❌ retweeted
Huggingface got breached! And we will see same pattern moving further, the cloud misconfigs gonna be weakest link and will amplify the blast-radisus.. 🧵 For iniitial foothold it will be either your code, agents, or simply the saas, third-party dependencies.. as I have shown in my Metabase, Posthog blogs. huggingface.co/blog/security…
1
6
31
3,918
Explaining bugs to triagers these days be like...
1
19
doc=new DOMParser().parseFromString(` <select> <button> <noscript> <selectedcontent></selectedcontent> </noscript> </button> <option> <style></noscript><img src=x onerror=alert()></style> </option> </select>`,'text/html'); document.write(doc.body.innerHTML);//🔥
4
25
3
268
26,629
like what’s even going on
10
35
5
286
7,445
Structha❌ retweeted
Good lord 🤮
25
58
24
416
331,209
セキュリティリサーチャー RyotaK @ryotkak の技術ブログを公開しました。 今回、Claude Code GitHub Actions の権限制御を外部の GitHub Issue 経由でバイパスし、ワークフロー権限を悪用できる脆弱性、並びにそれに付随する設定ミスを発見・報告しました。 当該の脆弱性は v1.0.94 で修正済みですが、設定ミスについては各リポジトリにて対応が必要であるため、当該製品を利用されている場合は設定の見直しと実行ログの確認を推奨します。 flatt.tech/research/posts/po…
32
4
108
49,956
Structha❌ retweeted
Posting a mini XSS challenge! Goal is to pop an alert. I believe this trick is not well known. Intended solution is chrome only. Thanks to @kevin_mizu for beta testing! Don't post solutions in the thread; DM only! xss.hashkitten.io/xss1.html
19
22
9
211
64,029
That's my chain — a full chain w/ logic bugs only! No memory corruption, no AI, and of course no collisions at all 😉
Confirmed! Orange Tsai (@orange_8361) of DEVCORE Research Team (@d3vc0r3) chained 4 logic bugs to achieve a sandbox escape on Microsoft Edge, earning $175,000 and 17.5 Master of Pwn points. Full win! #Pwn2Own #P2OBerlin
108
361
41
2,581
225,255
Structha❌ retweeted
nah im just not gonna run npm install anymore
178
415
44
8,343
387,590
Structha❌ retweeted
We responsibly disclosed the issue to @GitHub, who deployed a fix on GitHub.com the same day (!) and released patches for all supported GHES versions. GitHub Enterprise Server customers are strongly encouraged to update immediately.
3
27
2
260
39,478
Structha❌ retweeted
I started playing CTFs in 2022, and LLMs definitely changed the **competitive** CTF scene a lot, especially since mid-2025. I also started using LLMs in late 2025. Yes, those models did one-shot many challenges, but what's the fun of slopping them? I learned absolutely nothing 🥲
21
96
13
606
109,538
Structha❌ retweeted
i built an entire x86 CPU emulator in CSS (no javascript) you can write programs in C, compile them to x86 machine code with GCC, and run them inside CSS
317
1,017
265
9,894
1,078,450