Pentesting, scripting, pwning!

127.0.0.1
Joined January 2019
Input payload obfuscation is a real game changer here. No AMSI or ETW bypass needed and memory scanner evasion 👀
RustPack Release 1.8.0 was shipped to our customers recently. Short Blogpost with the most relevant new features for everyone here 🔥🔥 msecops.de/blog/posts/rustpa… #RedTeam #OST #Pentest #Maldev
2
28
161
9,618
S3cur3Th1sSh1t retweeted
LLMs...Letting me do fun things I never would have wasted time on. "I reviewed all 30 public GitHub repos for PHP2Shell (CVE-2026-109618 / CVE-2026-109619) by reading code only. The slide has the full grouped table; the headline findings: Nothing works against a real target. Every genuine memory-corruption chain is lab-bound: it needs exact per-build offsets, display_errors=On, a single prefork mod_php worker, and a specific image. Independent reviewers (allureluoli, dinosn, Gi1gamesh123) and the leaked primary source itself all converge on "no public artifact achieves code execution" on the patched core bug. Every real shell in these repos comes from an app-side LFI or deserialization sink, not the CVE. Three are original and real, all lab-only. 9bie (the source of the Set-Cookie leak chain), Marven11 (the most sophisticated, a true in-band leak), and Karasawa2025 (whose "Fermat" troll description hides a working ROP + display_errors=off exploit). These are the only ones with a genuine ASLR-defeating leak primitive that is their own. Most are copies. One original (9bie) spawned five derivatives: - twili8 is an outright uncredited rip-off: its own README still says git clone 9bie/... and the Docker files are byte-identical. - godylockz and xuehuolll are byte-identical to each other. - dinosn and 3em0 are credited ports that add value. Three are mislabeled. iQingshan, KarimUD7 (≈98% the same code), and Gi1gamesh123 exploit a different bug entirely (the Calif unserialize var_hash UAF) against their own planted endpoints, filed under the php2shell CVE numbers. The rest is noise. The most-starred repo (ikow, 905★) delivers the least: broken or stubbed chains with the two "real" ones paywalled behind Substack. eness (558★) is a leakless forge that can't defeat ASLR. syrex1013 ships AI-generated fake CVEs in a side directory. Whackermelon hallucinates a non-existent openai/php2shell-checker. lcfr-eth is a parody with a memecoin address, and Icex0 is an empty repo. The genuinely honest work is the crash labs (allureluoli, slabbdev, 0x4148), which prove the bug without claiming RCE. The ASLR column, star counts, copy lineage, and the specific "tell" for each repo are all in the table. The page is private to your account; use the Share menu if you want to send it to the team"
17
46
1
237
21,357
S3cur3Th1sSh1t retweeted
🦛🦛🦛Microsoft patched PetitPotam this October: EFSR now only resolves local paths. This means WebDAV to LDAP Coercion is fixed! Remaining methods for clients are WSP (coercing SMB) and PrinterBug (coercing RPC), but both cannot be relayed to LDAP 💀💀💀
9
98
5
285
18,849
S3cur3Th1sSh1t retweeted
RustPack Release 1.8.0 was shipped to our customers recently. Short Blogpost with the most relevant new features for everyone here 🔥🔥 msecops.de/blog/posts/rustpa… #RedTeam #OST #Pentest #Maldev
14
1
76
11,558
When your only authorization is JavaScript client side. And you can make yourself admin in 20 minutes. Than you know this was vibe coded. What is happening in 2026? 🤣
Doing an WebApp Pentest today. And this WebApp is 95% likely fully vibe coded. Authorization issues everywhere. Logical issues everywhere. Its like an CTF. And big consulting company likely won a tender because of lowest price. Happy birthday the next years will be great! 🫡🤪
10
9
162
13,050
Doing an WebApp Pentest today. And this WebApp is 95% likely fully vibe coded. Authorization issues everywhere. Logical issues everywhere. Its like an CTF. And big consulting company likely won a tender because of lowest price. Happy birthday the next years will be great! 🫡🤪
13
5
3
228
24,342
1.5 days later Qwen 3.8 Flash Next finished the first exemplary driver exploit PoC for PPL disable. Not listed on loldrivers not on the MS Blacklist. I guess many more to follow. GLM 5.3 Flash was not needed for this one 🧐
12
18
3
221
19,346
S3cur3Th1sSh1t retweeted
The TL;DR of what Anthropic just said: 1.) GLM-5.3 is as good as Mythos for exploit development. 2.) Unlike Claude, GLM-5.3 gives you the results you pay for. 3.) Governments should ban AI models which are as good as theirs but are not made by them. The funniest part is how Anthropic admitted self-reflectively that the lack of guardrails may actually be benefiting the defenders working to secure their systems. 🤪 Something they never wanted to allow, because of possible misuse. I don't get it, but I feel Anthropic should at least put a note at the very bottom if they are doing paid advertising to promote GLM-5.3. 😜 Source: anthropic.com/research/glm-5…
37
172
12
1,398
56,301
Qwen 3.8 Flash is decompiling thousands of drivers 24x7 searching for vulnerabilities while in parallel trying to build PoC exploits for some found vulns. Partially reaching 160 tok/s on two Sparks. No limit, no guardrails. This is what local AI can be used for perfectly fine! 🔥
21
76
7
1,062
54,114
Group3r from @mikeloss also ported to Python now with a beautiful HTML report for easy review: github.com/S3cur3Th1sSh1t/Py…
3
10
3
83
7,376
Anyone likes Snaffler? Want to run it from Linux with a nice HTML report and filtering options? Now you can: github.com/S3cur3Th1sSh1t/Sn…
6
43
1
205
12,419
Opus 4.8 says no because of cyber. Ok than let Opus 5.0 do it 🤣
5
7
137
14,831
While on the train I was wondering how Claude Code is sending messages from one session to another. This is how and you can manually inject "teammate" messages yourself: github.com/S3cur3Th1sSh1t/cl…
2
5
45
5,488
S3cur3Th1sSh1t retweeted
New Blogpost regarding to "Backdooring Open-Weight Models" just published by @ShitSecure: msecops.de/blog/posts/backdo…
22
1
74
12,111
First offensive talk today from Karan Raheja and @IndiShell1046 about weaponising IIS for Active Directory Post Exploitation. 🙌 @MCTTP_Con
2
5
1
23
3,773
S3cur3Th1sSh1t retweeted
.@ShitSecure & @KlezVirus sharing the work in their – really great – @MCTTP_Con talk ;-)
3
6
13
2,718
S3cur3Th1sSh1t retweeted
Can LNK files ever be trusted? ⚡ My latest blog post demonstrates several new LNK abuse methods, allowing you to fully spoof the target shown in Explorer. It also introduces tools to create your own LNKs, and detected spoofed ones yourself. 🐬 wietzebeukema.nl/blog/trust-…
11
232
7
1,005
145,431
Some new LNK abuse techniques from @Wietze at @MCTTP_Con 🔥
4
19
87
6,078
And another DCOM Lateral Movement technique released @MCTTP_Con by Shebin Mathew 🔥
2
30
138
7,556
S3cur3Th1sSh1t retweeted
I’m not worried about the future of pentesting and here’s why. The automated pentesting trend is following a similar trajectory as vulnerability scanning. Organizations only interested in compliance or those who have very small environments or budget will just go the automated route. Those who truly want to improve and who want expert guidance and consulting will go the manual or human-led route. The good thing is the automated route has gotten better and will continue to. But so will manual/human-led. There’s plenty of organizations to serve and to help in both categories. 🫡
12
9
1
54
5,700