Jump to content

Recommended Posts

Hello,

Pretty sure these detections are false positives but figured I would be sure. Made a word document and went to print as usual but was blocked from printing. Around exactly this time I also recieved a notification from microsoft about peronalizing settings which I closed so not sure if that caused a detection as well. Note I was on an older version of bytes 4.5.4.168 but updated and recieved the same detection when trying to print from word. I tested using a test print and it went through so Im pretty certain its something in bytes not liking word or office.  Saw people with similar issues before from reading through the forums. Everything was working fine until today. Wondering what settings may be causing this to occur if it is indeed a false positive. Long time lurker, first time poster, thanks in advance for taking a look!

First detection as follows

Malwarebytes
www.malwarebytes.com

-Log Details-
Protection Event Date: 4/14/22
Protection Event Time: 8:53 AM
Log File: e1859a8b-bbf1-11ec-b09f-e02be962260d.json

-Software Information-
Version: 4.5.4.168
Components Version: 1.0.1599
Update Package Version: 1.0.53647
License: Premium

-System Information-
OS: Windows 10 (Build 19044.1586)
CPU: x64
File System: NTFS
User: System

-Exploit Details-
File: 0
(No malicious items detected)

Exploit: 1
Malware.Exploit.Agent - Process Hollowing Protection, , Blocked, 0, 392684, 0.0.0, , 

-Exploit Data-
Affected Application: Microsoft Office Word
Protection Layer: Protection Against OS Security Bypass
Protection Technique: Process Hollowing Protection
File Name: 
URL: 

(end)

Second detection

Malwarebytes
www.malwarebytes.com

-Log Details-
Protection Event Date: 4/14/22
Protection Event Time: 8:54 AM
Log File: fecfa6f8-bbf1-11ec-8f73-e02be962260d.json

-Software Information-
Version: 4.5.4.168
Components Version: 1.0.1599
Update Package Version: 1.0.53647
License: Premium

-System Information-
OS: Windows 10 (Build 19044.1586)
CPU: x64
File System: NTFS
User: System

-Exploit Details-
File: 0
(No malicious items detected)

Exploit: 1
Malware.Exploit.Agent - Exploit payload process blocked, C:\Windows\splwow64.exe C:\Windows\splwow64.exe 8192, Blocked, 0, 392684, 0.0.0, , 

-Exploit Data-
Affected Application: Microsoft Office Word
Protection Layer: Application Behavior Protection
Protection Technique: Exploit payload process blocked
File Name: C:\Windows\splwow64.exe C:\Windows\splwow64.exe 8192
URL: 

(end)

 

Link to post
Share on other sites

@Porthos Thank you porthos I was able to print with no detection. I think now that penetration testing was what was causing the detection. I like having it on and know it can spit out some false positives but was concerned since I personally havent had any issue untill now. Weird that it just started up today though. If theres any chance it wasnt a false positive someone feel free to let me know but that was likely the issue.

Link to post
Share on other sites

10 minutes ago, Testing542 said:

I think now that penetration testing was what was causing the detection. I like having it on and know it can spit out some false positives but was concerned since I personally havent had any issue untill now.

This is just another instance of enabling non default settings that should not be enabled. End result is False Positives that scare users into thinking there is an issue when there is not.

Same goes for the scan for rootkit setting and the expert system protections settings.

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.