Jump to content

ExploitPayloadfileBlocked for me


p060477

Recommended Posts

same big issue to me...:

 

Malwarebytes
www.malwarebytes.com

-Dettagli log-
Data evento di protezione: 02/09/23
Ora evento di protezione: 21:38
File di log: 4097964e-49c8-11ee-b7dd-74d435bb1f97.json

-Informazioni software-
Versione: 4.6.1.280
Versione componenti: 1.0.2117
Aggiorna versione pacchetto: 1.0.74775
Licenza: Premium

-Informazioni sistema-
SO: Windows 10 (Build 19045.3324)
CPU: x64
File system: NTFS
Utente: System

-Dettagli exploit-
File: 0
(Nessun elemento nocivo rilevato)

Exploit: 1
Exploit.PayloadProcessBlock, C:\WINDOWS\system32\cmd.exe C:\WINDOWS\system32\cmd.exe \S \D \c type da.txt, Bloccato, 701, 392684, 0.0.0, ,

-Dati exploit-
Applicazione interessata: cmd
Livello di protezione: Application Behavior Protection
Tecnica di protezione: Exploit payload process blocked
Nome file: C:\WINDOWS\system32\cmd.exe C:\WINDOWS\system32\cmd.exe \S \D \c type da.txt
URL:

 

(end)

 

 

this is a real bug...how to solve it...??....

Link to post
Share on other sites

  • Staff

Hi,

Thanks for posting. 

The hourly definition updates are not for the exploit protection module. Exploit protection module updates are more at a "once a month" cadence, sometimes even longer. It is a coincidence that the blocks disappeared with the def update. I would like to take a deeper look at your logs to figure out what causes this FP.

Can you please

  1. Turn on "Even log data" toggle Refer the below screenshot:
  2. Reproduce the block
  3. and then grab the below files:
  4. Please get us the following two files
  • C:\ProgramData\Malwarebytes\MBAMService\logs\mbae-default.log
  • C:\ProgramData\Malwarebytes\MBAMService\logs\MBAMSERVICE.log  

   

image.png.c10bd5284e9794417cfaf8dc18a3d8cf.png

Link to post
Share on other sites

the BUG issue is coming back...:

Malwarebytes
www.malwarebytes.com

-Dettagli log-
Data evento di protezione: 06/09/23
Ora evento di protezione: 10:40
File di log: 05585836-4c91-11ee-a664-74d435bb1f97.json

-Informazioni software-
Versione: 4.6.1.280
Versione componenti: 1.0.2117
Aggiorna versione pacchetto: 1.0.74897
Licenza: Premium

-Informazioni sistema-
SO: Windows 10 (Build 19045.3324)
CPU: x64
File system: NTFS
Utente: System

-Dettagli exploit-
File: 0
(Nessun elemento nocivo rilevato)

Exploit: 0
(Nessun elemento nocivo rilevato)


(end)

 

this is a real NIGHTMARE.....pls FIX it for heaven sake....

Link to post
Share on other sites

On 9/5/2023 at 8:36 PM, Arthi said:

Hi,

Thanks for posting. 

The hourly definition updates are not for the exploit protection module. Exploit protection module updates are more at a "once a month" cadence, sometimes even longer. It is a coincidence that the blocks disappeared with the def update. I would like to take a deeper look at your logs to figure out what causes this FP.

Can you please

  1. Turn on "Even log data" toggle Refer the below screenshot:
  2. Reproduce the block
  3. and then grab the below files:
  4. Please get us the following two files
  • C:\ProgramData\Malwarebytes\MBAMService\logs\mbae-default.log
  • C:\ProgramData\Malwarebytes\MBAMService\logs\MBAMSERVICE.log  

   

image.png.c10bd5284e9794417cfaf8dc18a3d8cf.png

hi, just turned on, also if it is clearly written : not recommended....

anyway now the issue has disappeared again....

it comes in and out randomly....

it really seems a joke...a very ugly and very upsetting one....

:(

Link to post
Share on other sites

we are very very upset

weeks in digital era are a to huge quantity of timre....

and what about the data logs you asked...??

they are more then 13mb of data...text data...so a very huge quantity...

what you do with our so personal data...??

what about our privacy

pls reply clearly and stop simply cancelling posts you dislike...

thxs

 

Link to post
Share on other sites

  • Root Admin

Good day @p060477

I'm sorry to hear that you're upset, but without being able to duplicate on our own we do need logs in order to attempt to track down the root cause. Then work on a solution to correct the issue without possibly causing other unexpected issues.

In the future if you do not wish to provide logs for any type of issue, that's perfectly fine. Submitting logs is voluntary. I'm sure there are others that may be willing to provide logs.

 

There is not a day that goes by that Microsoft does not automatically collect data from all Windows systems as they need it to help improve their products too.  The complexity of software today is completely different than it was just a few short years ago and quick fixes are not always possible. In some cases there can be hundreds of thousands of lines of code or in more complex software there can be millions of lines of code and it only takes one or two characters to be written wrong to possibly cause issues. Finding and correcting that, can be like finding the proverbial needle in a haystack some times. Other times one can quickly spot what is going wrong in the code and you can work on a better solution pretty quickly.

Thank you

 

Edited by AdvancedSetup
Updated information
  • Like 2
Link to post
Share on other sites

  • 2 weeks later...

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.