Open MalwareTips in Safari and tap Share. You may need to open the Page Menu first.
Choose Add to Home Screen. If it is not listed, use Edit Actions to add it.
Keep Open as Web App enabled if shown, then tap Add.
Android
Open MalwareTips in Chrome or another browser that supports app installation.
Open the browser menu and look for Install app, Install and create shortcut, or Add to Home screen.
Choose Install and confirm. Wording varies by browser.
Desktop
Chrome: use the install icon in the address bar, or the menu under Cast, save and share.
Edge: open the menu, then More tools, Apps and Install this site as an app.
Safari on Mac: choose Share or File, then Add to Dock. Firefox on Windows: look for the web apps button in the address bar.
If you cannot find an install option, update your browser or use its bookmark option to keep MalwareTips close.
Keep up with your conversations
After installation, open the app and sign in. Enable push notifications in Preferences if you want alerts. On iPhone and iPad, push requires a Home Screen web app and iOS or iPadOS 16.4 or later.
uBlock Origin Lite (uBOL) on Chromium does not save “custom filters” as a readable .txt file. They’re stored in the extension’s local storage (i.e., Chromium’s extension storage / LevelDB). ([reddit.com](https://www.reddit.com/r/uBlockOrigin/comments/1mk6psy?utm_source=openai))
Where uBOL custom filters are stored (what to exclude)
On disk, the relevant location is your Chromium profile’s:
Local Extension Settings\<uBOL-extension-ID>\ (this is where extension “local storage” lives on Windows; uBOL’s per-site custom filter entries show up as keys starting with “site.” when inspected in DevTools) ([reddit.com](https://www.reddit.com/r/uBlockOrigin/comments/1mk6psy?utm_source=openai))
Typical Windows paths (Chromium browsers)
Replace:
<PROFILE> with Default, Profile 1, etc.
<uBOL_ID> with uBOL’s extension ID (see next section)
Extra-safe way to confirm you’re looking at the right data
This is also useful if you want to be 100% sure you’re excluding the right storage:
chrome://extensions -> uBOL -> click the service worker link
DevTools -> Application tab -> Extension Storage -> Local
uBOL’s custom entries are typically the ones whose keys start with “site.” ([reddit.com](https://www.reddit.com/r/uBlockOrigin/comments/1mk6psy?utm_source=openai))
Sandboxie note (security impact)
If you add a Sandboxie “direct access / exclusion” for that folder, you’re intentionally allowing the sandboxed browser to write outside the sandbox to persist uBOL settings. That reduces containment. A safer pattern is to keep the sandbox persistent or use Sandboxie recovery to copy out only what you need, rather than giving permanent direct access to parts of the browser profile.
If you want to keep Sandboxie containment as strong as possible, the main thing is to keep that exclusion as narrow as you can (only the uBOL extension ID folder, not the whole “Local Extension Settings” tree), since it’s one of the few places a sandboxed Chromium session can persist changes outside the sandbox.
Recently browsing
Members who viewed this thread in the last 5 minutes