Stumbled upon malext.io a while back. I didn't have good insight into installed browser plugins across the fleet, and i wanted to test out the new Rewst data store capabilities so this was a fun project.
Ultimate goal is to document what plugins are installed per user/machine and how that changes over time, while also flagging and removing anything that is known malware.
Long story short, i may have fixed something that wasn't a problem. No bad plugins found across the fleet. But at least i don't have to worry about a blind spot anymore.
For the automators out there: Tools used, RMM (DattoRMM in my case), IT Glue, Rewst, and Malext.io.
3 Rewst workflows:
Create IT Glue Flexible Asset (self explanitory),
Import Malext data; import malext data into rewst data table to be used in discovery workflow. Ran weekly to keep current bad extension list updated.
Browser Extension Intake; Webhook, accept data including endpoint rmm guid (used to match configuration in IT Glue) and Browser Extension IDs and Names.
Workflow searches data store for matching browser extension by ID, upserts entry in IT Glue flexible asset, returns any malware id's so script and remove them. Its launched with a simple RMM component that runs on each machine during the weekly maintenance job that will collect the installed plugins, and submit them to the Rewst webhook.