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 💀💀💀

S3cur3Th1sSh1t@ShitSecureOct 17
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @mrgretzky
Good vibe code 1o1’s. Had the same experiences this year.

S3cur3Th1sSh1t@ShitSecureOct 16
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @mrgretzky
🤣

S3cur3Th1sSh1t@ShitSecureOct 16
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @mrgretzky
Disclaimer: AI was used to develop the extension. UX, UI design, and minor code tweaks originated from a human brain. Code was read using human eyes. 😂
I may need to also use that phrase later.

S3cur3Th1sSh1t@ShitSecureOct 14
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @Void_Sec
Closed Source is the new Open Source in 2026

S3cur3Th1sSh1t@ShitSecureOct 13
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @mrgretzky @x33fcon
Both highest stats nice 🔥

S3cur3Th1sSh1t@ShitSecureOct 10
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @eversinc33
That was created by my locally hosted Minimax H3 :-)

S3cur3Th1sSh1t@ShitSecureOct 10
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
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
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

S3cur3Th1sSh1t@ShitSecureOct 7
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @Jean_Maes_1994 @grok
Well for offensive security tasks people need to fall back to opus 4.6 depending on the task. Models that run on the sparks are similar to opus 4.8 on benchmarks. Frontier in general vs frontier in maldev for example is not the same. 🤷♂️

S3cur3Th1sSh1t@ShitSecureOct 7
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @Jean_Maes_1994 @grok
Definitely depends on the use cases true 👍

S3cur3Th1sSh1t@ShitSecureOct 7
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @Jean_Maes_1994 @grok
With API costs this is easy and fast. I compared my spark overall input output token vs API costs and same tokens for Claude Opus would have been more than 70k € already. In Subscription token that would be 10-12 Months 200€ subscription now? 24x7 usage over 6 weeks.

S3cur3Th1sSh1t@ShitSecureOct 6
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @decoder_it
Exactly this is what Claude implemented got me this year in an internal WebApp. Even Opus. 🤷♂️ if the prompt didn’t mention server side validation why should it.

S3cur3Th1sSh1t@ShitSecureOct 6
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @NinjaParanoid
Yup that is what’s happening. Would have never expected that one year ago 😂

S3cur3Th1sSh1t@ShitSecureOct 6
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
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? 🤣
S3cur3Th1sSh1t@ShitSecureOct 6Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
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! 🫡🤪

S3cur3Th1sSh1t@ShitSecureOct 6
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
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! 🫡🤪

S3cur3Th1sSh1t@ShitSecureOct 4
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @wilcosec
Self created. Or claude did create it with my instructions :P

S3cur3Th1sSh1t@ShitSecureOct 4
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @Ali852561939151
Zero help fully autonomous. Custom self created harness created by Claude. Ghidra and python capstone and rizzin for reversing. Its a react loop with handover each run similar to ralph loops.

S3cur3Th1sSh1t@ShitSecureOct 4
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @mihuofficial
Zero manual input anymore. Fully autonomous just pass all the drivers in and wait.

S3cur3Th1sSh1t@ShitSecureOct 3
Germany
GermanyConnected via Germany App StoreAccount-level information, not a live location or per-post device.
Replying to @LTE_Max
I had a dedicated mission before with source code analysis and this was one of the vulnerable results from that.




