How to uninstall LuLu on Mac

LuLu is a free, open-source firewall from Objective-See that blocks outgoing connections you have not approved. Once you approve its system extension and network filter, it is more than an app in Applications, so remove it with LuLu's own uninstall command rather than by dragging it to the Trash, and export your rules first if you want to keep them. This guide covers the official download and the Homebrew cask lulu.

Export your rules

Objective-See's LuLu page says rules can be exported and imported from the Rules menu, and that each profile keeps its own rules and settings. Export from every profile you want to keep before you uninstall.

Uninstall through LuLu

1. Click LuLu's icon in the menu bar and choose its uninstall option. The same page says quitting or uninstalling asks you to authenticate.
2. If you only copied LuLu into Applications and never approved its extension, quitting it from the menu bar icon and moving it to the Trash is enough.

Where its data lives

Finish LuLu’s own uninstall and verify the exported rules first. To clear leftover user preferences or caches, open each exact path below with Shift + Command + G in Finder and move only existing LuLu items you no longer need to the Trash. This step does not deactivate the network filter.

Check the result

pgrep -il lulu
systemextensionsctl list | grep -i lulu
ls -ld ~/Library/Preferences/com.objective-see.lulu*

• No output from pgrep means LuLu is not running.
• If systemextensionsctl list succeeds without errors, an empty filtered result means its registration list has no name matching lulu. A matching line can describe an active extension or one awaiting removal; read its status and use LuLu’s own uninstall command if needed. Query errors leave the result unknown.
• ls -ld printing "no matches found" or "No such file or directory" means no LuLu preferences file is left. A listed file means it is still there.

If you installed it with Homebrew

The lulu cask's zap list names four paths: caches and preferences under com.objective-see.lulu and com.objective-see.lulu.helper. None of them uses LuLu's bundle ID, so Mole can list them, taken from Homebrew's zap list for this app. They start unchecked with Remove data and settings with apps off; turning it on can preselect eligible app-owned data, so review each row. When any of them exists and stays unticked, Mole leaves out --zap and still moves the rows you selected to the Trash itself. Neither the zap list nor Mole deactivates the system extension; that is LuLu's own uninstall command's job.

Running the zap step yourself removes those four paths whatever you ticked in Mole:

brew uninstall --cask --zap lulu

To remove only the app:

brew uninstall --cask lulu

What Mole lists

For LuLu installed from the official download:

• Files filed under LuLu's bundle ID com.objective-see.lulu.app are selected by default.
• Mole can also list the four com.objective-see.lulu and com.objective-see.lulu.helper cache and preference paths, taken from Homebrew's zap list for this app. They start unchecked with Remove data and settings with apps off; turning it on can preselect eligible app-owned data, so review each row.
• LuLu's system extension and network filter are not listed.

What this test covered

On September 19, 2026, only LuLu.app was copied from the official download into Applications; its system extension and network filter were never approved. It ran as a menu bar app and was removed with a Preview build of Mole 1.15 (build 277); there was no Homebrew receipt. Mole's startup list showed LuLu's embedded login item as a confirm-only row, and that row was gone after the app was removed. An approved network extension, rules, profiles and the Homebrew cask were not tested, so the uninstall steps above come from Objective-See's page, not from this test.