Search the Community
Showing results for tags 'roboform'.
Found 2 results
-Log Details- Protection Event Date: 11/17/17 Protection Event Time: 6:13 PM Log File: 514a9862-cbf5-11e7-a756-f48e388b9cee.json Administrator: Yes -Software Information- Version: 184.108.40.2063 Components Version: 1.0.236 Update Package Version: 1.0.3286 License: Premium -System Information- OS: Windows 10 (Build 16299.64) CPU: x64 File System: NTFS User: System -Exploit Details- File: 0 (No malicious items detected) Exploit: 1 Malware.Exploit.Agent.Generic, , Blocked, , ,0.0.0 -Exploit Data- Affected Application: Mozilla Firefox (and add-ons) Protection Layer: Protection Against OS Security Bypass Protection Technique: Exploit ROP gadget attack blocked File Name: URL: (end) I have uninstalled with plugins removed, once I installed Roboform it crashed because Malwarebytes blocked it. mb-check-results.zip
Software (all current as of Jan 13, 2018) OS: Win 7 x64 SP1 MB: Premium 3.3.1 AV: eSet v11 Roboform: 220.127.116.11 Chrome x64 When I'd run Chrome with Roboform enabled, I'd notice lag and high CPU use (2-5% constant) for the Roboform process (rf-chrome-nm-host.exe) attached to Chrome. This does not occur when I use Firefox x64 with Roboform enabled - the same executable is used for Firefox and the filename is not specific for Chrome (weird huh?). I used Procmon (from Sysinternals) to see what the Roboform process was doing only when Chrome was in use. There's a constant registry lookup cycle along with file lookup. I had been trying to figure out what the issue was, but finally involved the Roboform support team. They looked at my Procmon log and ran some internal tests - they said that eSet and/or MB were injecting into those processes. I tested many scenarios and in the end they were correct - MB was the culprit. With MB disabled I can run Chrome with Roboform and no spikes in CPU occur. I then went further to test a brand new Chrome profile with nothing enabled other than Roboform - same issue. I then added the Roboform executable in question to the MB exclusions list, but the CPU issue still exists only in Chrome. The CPU issue with this process only happens with MB enabled, so I now have to choose between either MB or using Roboform in Chrome. Ideas?