<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Hey #oss #security folks,]]></title><description><![CDATA[<p>Hey <a href="https://mas.to/tags/oss" rel="tag">#<span>oss</span></a> <a href="https://mas.to/tags/security" rel="tag">#<span>security</span></a> folks,</p><p>Someone is running a spear phishing attack against my tiny business, which feels unexpected given the size of my organization (just me).</p><p>Could you recommend some simple ways I can stop the attack? It involves extremely well-designed emails from various compromised email addresses that impersonate the SendGrid system and use very plausible messages.</p><p>My main concern is that this could evolve into something more sinister. I don't mind blocking all emails containing "SendGrid," but I would rather do something that could make those people move on and not come back.</p><p>Thanks so much!</p>]]></description><link>https://board.circlewithadot.net/topic/c5663c84-79a6-4f7e-92aa-6c4379d53802/hey-oss-security-folks</link><generator>RSS for Node</generator><lastBuildDate>Sat, 06 Jun 2026 00:47:39 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/c5663c84-79a6-4f7e-92aa-6c4379d53802.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 28 May 2026 18:11:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Hey #oss #security folks, on Thu, 28 May 2026 18:44:11 GMT]]></title><description><![CDATA[<p><span><a href="https://mas.to/@analog_cafe">@<span>analog_cafe</span></a></span> oof - tbh, not sure if there was a specific "do this and they disappear" remedy, sorry.  Things to harden your org however. Short run - make sure your EDR is clued in to the issue either via IOCs you can harvest from the phish, or if its a managed service letting them know. The 'sinister evolution' will likely take the shape of loading RATs on your endpoints (especially if you're passwordless), which seems to be next pivot when attackers cannot obtain credentials. Be cautious even with 'safe' tools that aren't specifically RATs like teamviewer, or screenconnect for example.</p><p>Other measures - alert on anomalous login. activity. What is anomalous depends on your org, but if its just you, then I would start by alerting on odd geographic logins from unexpected IPs/ASNs, novel UAs, even things outside of 'normal' business hours might be helpful. If you don't have that kind of telemetry then that's a good starting point. Also alerting on account changes; such as new forwarding rules is a great way to detect compromise</p><p>Blocking on known bad indicators such as sendgrid will stem the issue for a bit, but attackers pivot, so its a bit of whack-a-mole. But if you're small enough, and whack enough moles, the attackers leave for easier targets. Unfortunately - one compromise makes never going away worth it. </p><p>Likely you're already doing this, but strictly segregate and harden (MFA, alerting etc) your admin accounts from your user accounts - if attackers compromise your user account they won't get the keys to the whole kingdom.</p><p>That's simply the low hanging fruit, I am certainly more capable security folks will chime in, but hopefully this get you to a relatively safe place.</p><p>Hope this is helpful but otherwise good luck!</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/chronovore/statuses/116653677034925208</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/chronovore/statuses/116653677034925208</guid><dc:creator><![CDATA[chronovore@infosec.exchange]]></dc:creator><pubDate>Thu, 28 May 2026 18:44:11 GMT</pubDate></item></channel></rss>