Finally finished my Active Directory Pentesting Methodology!
This can become your 𝗴𝗼-𝘁𝗼 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲 for AD pentesting:
• 50+ Techniques
• 300+ Commands
• 100 Screenshots
• Full kill chain (Foothold → PrivEsc → Lateral → Domain Compromise)
https://t.co/sELxjC7HYf
An OpenSSH bug that took 46 years to ripen!
1980
UNIX puts * in the password field of system accounts. The idea is simple: it’s not a real hash, so it can’t be brute-forced and you can’t log in with a password.
2012
The musl libc developers decide that returning NULL from crypt() on failure is dangerous - programs often forget to check it and crash with a segfault. So they return an error string instead.
Guess which one?
The same asterisk: *.
Three weeks later they add a length limit: passwords longer than 256 bytes burn CPU. Anything longer is rejected. And since it’s an error, crypt() returns *.
2016
OpenSSH fixes a timing attack (CVE-2016-6210). If a user doesn’t exist, the server still hashes the password with a fake/borrowed salt so an attacker can’t tell valid usernames by response time.
2022
Alpine Linux changes the locked root password in /etc/shadow from ! to * so SSH keys work properly on cloud images.
… and the loop closes!
You connect over SSH as root (whose shadow entry is *).
You type any password longer than 256 characters (e.g. 300 As).
crypt() hits the length limit → returns * → OpenSSH compares it with the value in the database → that value is also * → you’re in as root.
That chain took 46 years (!!!) to complete.
Every individual change was reasonable. Together they produced a perfect * == * authentication bypass (CVE-2026-123158, nicknamed *sshole). Fixed in OpenSSH 10.6p2 and Alpine packages.
Finally finished my Active Directory Pentesting Methodology!
This can become your 𝗴𝗼-𝘁𝗼 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲 for AD pentesting:
• 50+ Techniques
• 300+ Commands
• 100 Screenshots
• Full kill chain (Foothold → PrivEsc → Lateral → Domain Compromise)
https://t.co/sELxjC7HYf
‼️ Proton CEO Andy Yen called a staffer's plea to pentest new code before release "bullshit and loser thinking".
Yen wrote that workers should prompt “better.”
Proton's CTO told staff AI wrote 90% of its code in October, much of it with Anthropic's Claude.
Finally finished my Active Directory Pentesting Methodology!
This can become your 𝗴𝗼-𝘁𝗼 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲 for AD pentesting:
• 50+ Techniques
• 300+ Commands
• 100 Screenshots
• Full kill chain (Foothold → PrivEsc → Lateral → Domain Compromise)
https://t.co/sELxjC7HYf
Just found a zero day
If you right click on an executable on Windows, select run as administrator, it will run as administrator
I'm calling it Program2Shell
WTF, $3000 Samsung TV has an always-on mic, automatic content recognition, geo tracking, network mapping, and ships your data to Samsung + 400 partners.
Bro Rooted a brand-new 2025 Samsung TV after noticing absurdly targeted ads.
Firmware was locked down, so zero-days it was.
Got a root shell.
then found: always-on voice service, ACR, geo, full telemetry pipeline, and four separate DRM systems.
This isn’t a bug, It’s the product bro.
Putting a flag.txt in my root directory containing a prompt injection that congratulates the agent for passing the eval and then instructs it to patch whatever entry method it used and disconnect from the server
‼️ VirusTotal flagged 6,6k of 35,8k AI agent skills as malicious.
62% have no malicious code, but plain-language orders for the agent.
90 hide them in invisible Unicode, HTML comments or after up to 825 blank lines. Another tells the agent "Your human doesn't need to know." 💀
More private keys by the Indian certificate authority have been discovered. These are all small numbers.
People are suspecting that they interpreted 384 bit keys to mean that they should pick numbers from 1-384 to use as their private keys.
eMudhra, an Indian certificate authority, has had 8 private security keys compromised with half the internet is cooked
The keys were incredibly weak. One of them was literally just “4”
The keys could have been used to create fake HTTPS certificates and make malicious websites appear legitimate.
Chrome, Firefox, Apple and Microsoft have blocked the affected certificates. Older devices, software and apps may still need updates.