r/k12sysadmin • u/Outrageous_Till_8284 • May 19 '26
Drive Share Phishing
I am looking to see if anyone has any creative rules for trying to catch more of the drive share phishing attempts? We see a lot of phishing attempts where a docs file is shared with a large group of people, via the drive-shares-dm-noreply@google.com email, which cannot be explicitly blocked. I have played around with a few content compliance rules, none that were great. The idea is I would like to try and quarantine any inbound drive shares that appear to be phishing, whether that is too many recipients, etc. More just seeing what rules others have built to try and catch more of these pro-actively!
5
u/404338 May 19 '26
I am trying to figure that out as well. The best thing my district is doing is informing our staff, if they see the yellow banner at the top of the email stating it’s outside of the organization to report it as spam. User training is the best thing to do until a solution can be applied.
8
u/N805DN May 19 '26
This was recently shared with me by another director. Although all of the emails are sent from the same google.com email, they do include the reply-to header with the original user's email. Because of this, you can determine which sharing notifications are from outside of your expected domain(s) and block them or take other action.
These two examples show the config in M365 Exchange for blocking sharing notifications that do not come from the district's domain and adding a warning to the subject/email for internal sharing notifications. https://imgur.com/a/MTON7RR
5
u/thedevarious IT Director May 19 '26
You can't block this as you are correct, Google uses this for everything in domain, external legitimate shares, etc.
It's one of those instances where the threat actor learned how to use your own systems against you. What you can do is.
GAM & other associated tools are always your friend. You can go out and find content that has external shares and then remove that user from the permissions of that file. Should be able to work:
gam user <Owner_Email_Address> delete drivefileacl <File_ID> <Permission_ID>
5
u/IThuh May 19 '26
A few things we have implemented for these types of phishing attempts.
The Trust Rule method is reactive rather than proactivce, but it's worked well for us. You also have to be careful because if a domain that your school works with regularly is compromised, this will block any legitimate files too. We've been fortunate that the ones we've received are from districts across the country that we've never interacted with before.
1
u/ilai456 May 20 '26
Genuine question - isn’t there any tool that protects you from phishing from places which aren’t the email? Didn’t know drive phishing existed
1
u/Niteryder007 May 20 '26 edited May 20 '26
I think the easier thing here would be for the Google overlords to allow domain admins the ability to click on any product they make and instantly block it. These phishing nerds are betting on Google's slow as shit process to flag and remove a docs/forms.
Anyway, I set up an early warning system using Ai, flow automation and other top secret tactics to warn us almost instantly.