{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiahzwsav42ackkq7deqtmsjuz7kymzbjbmvhh6vtu4hjdk6ycxj2a",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkz5wfvmpch2"
  },
  "path": "/viewtopic.php?t=33402&p=273378#p273378",
  "publishedAt": "2026-05-04T05:51:49.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> The suggestion \"go into defender, \"restore\" the file, and report it to Microsoft\" is not a permanent solution.\n\nIf you want a more permanent solution, you can exclude the entire Pale Moon folder from Windows Defender detection.\n\nAlso, you can try installing Pale Moon from the Windows Store and see if that makes a difference.\n\n\"Changing the file a little bit\" wouldn't help anything, in fact the false positive is likely because the file isn't an exact match to previous versions.\n\nNote that the signature:\n\nTrojan:Win32/Posilod.EB!cl\n\nClearly indicates that cloud-based heuristics were used to flag a suspicious file rather than a definite detection of a virus or malware. It's approaching the point where files have to be on a whitelist and recognized by the system to not get flagged, honestly.\n\n* * *",
  "title": "Browser Support • Re: "Couldn't load XPCOM" - Browser is completely bricked.",
  "updatedAt": "2026-05-04T05:51:49.000Z"
}