Angerman 🦅<p>While I am at it anyway; <a href="https://infosec.exchange/tags/Phishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Phishing</span></a> meets <a href="https://infosec.exchange/tags/SMB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SMB</span></a>: Exploiting network trust to capture <a href="https://infosec.exchange/tags/NTLM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NTLM</span></a> hashes (<a href="https://infosec.exchange/tags/pentesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pentesting</span></a> fun)</p><p>One effective phishing method leverages SMB connections to capture <a href="https://infosec.exchange/tags/NetNTLM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NetNTLM</span></a> hashes for offline <a href="https://infosec.exchange/tags/cracking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cracking</span></a>, providing attackers with credentials for the next phase (for example social engineering or other tech attacks). Oh; BIT B.V. (bit.nl) did send my a set of abuse mails, … sorry 😆 … but very nice and thx 🙏🏼, anyway;</p><p>Exploit Path: Initial Phishing Vector: The attack starts with a phishing email or download website or something something, containing a payload (e.g., a malicious document or shortcut file, whatever, choose your poison). </p><p>The payload initiates an SMB request to the attacker-controlled server (`\\<C2IP>\share`), tricking the victim’s system into authenticating with it. Modern browsers like edge won’t fly; you need to get a bit more creative to execute this and no it’s not a hyperlink. Think Java. Or macro (although; meh). </p><p>Then we have SMB Request Redirection: Tools like Responder on the attacker’s C2 server capture NetNTLMv2 hashes during these authentication attempts. This works over IPv4 and IPv6, with IPv6 often prioritized in networks and less monitored. Hence <a href="https://infosec.exchange/tags/mitm6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mitm6</span></a>. But that’s another story. </p><p>Captured hashes are cracked offline using tools like <a href="https://infosec.exchange/tags/Hashcat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hashcat</span></a>, potentially giving credentials for further attacks. It’s also an excuse for my new RTX 5090 card. 😉</p><p>Observations from recent penetration tests where I executed this attack; </p><p>-Firewall Rules: not excisting … at all. 🥹<br>Many environments have outbound 'any-any' rules on firewalls, even on critical nets like Citrix farms. This unrestricted outbound traffic allows SMB authentication requests to reach attacker-controlled servers on the internet. And there is something with remote workers and open internet access lately… <br>-<a href="https://infosec.exchange/tags/Azure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Azure</span></a> and <a href="https://infosec.exchange/tags/2FA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>2FA</span></a> Gaps, here we go again (see <a href="https://lnkd.in/g2ctMEDG" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">lnkd.in/g2ctMEDG</span><span class="invisible"></span></a>); 2FA exclusions are another common issue:<br>- Trusted locations (e.g., `192.168.x.x` or specific IP ranges) configured to bypass 2FA/MFA.. intended to improve usability, such exclusions can be exploited once an attacker gains access to these "trusted" locations; simply put a VM inside a 192.168 range and chances are…. Good. </p><p>These misconfigurations reduce the effectiveness of otherwise robust security measures like MFA and firewall segmentation, giving attackers unnecessary opportunities.</p><p>The Takeaway: Attackers thrive on overlooked gaps in configuration. Whether it's outbound "any-any" firewall rules or MFA bypasses for trusted locations, these lapses provide unnecessary pathways for compromise. By combining phishing, SMB exploitation, and tools like Responder, we can target foundational weaknesses in even hybrid environments. I’ve seen soc’s only respond after mission target; because most are monitoring just on the endpoint (EDR/XDR), poorly.</p><p><a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CyberSecurity</span></a> <a href="https://infosec.exchange/tags/Phishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Phishing</span></a> <a href="https://infosec.exchange/tags/SMB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SMB</span></a> <a href="https://infosec.exchange/tags/NTLM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NTLM</span></a> <a href="https://infosec.exchange/tags/MFA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MFA</span></a> <a href="https://infosec.exchange/tags/FirewallSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FirewallSecurity</span></a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> </p><p>The meme is absolutely intended as shitposting. Sorry 🤣</p>