Is Fabasoft Folio 2020 safe?
Fabasoft Folio 2020 relays cookies from any visited page to the local Fabasoft native host when a first-caller web page opens the messaging channel.
The extension injects a content script on every page (<all_urls>) that listens for postMessage calls of type 'com.fabasoft.nm.sendpm20'. Because the origin check variable is null until the first message arrives, the first web page to send that message — regardless of origin — claims exclusive ownership of the native messaging channel. When the native host invokes Init or UpdateLoginToken, the background script reads all cookies for the originating page's URL via chrome.cookies.getAll and forwards them as a semicolon-delimited string to the 'com.fabasoft.nmhostpm20' native host process.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 20.3.1.24. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on every site you visit
<all_urls>
See the address and title of every tab you have open
tabs
Read and change cookies, including the ones that keep you signed in
cookies
Talk to a program installed on your computer, outside the browser's sandbox
nativeMessaging
Where it sends data
Destinations our analysis observed Fabasoft Folio 2020 contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- com.fabasoft.nmhostpm20 (local native host)
Fabasoft Folio 2020 sends data to com.fabasoft.nmhostpm20 (local native host). Named as a recipient in this extension's own analysis.