svchost.exe outbound connection blocked due to Trojan

[Aeacus]

Hi folks!

 

So, i've been using MWB Premium for years and thus far, i've been pleased. That is, until today, which got me worried and prompted me to make this topic.

 

Namely, i was dealing with my hobby on my desktop PC (image editing), with GIMP and PhotoScape open and got MWB Premium pop-up, of svchost.exe trying to establish outbound connection and it was blocked due to Trojan.

(Report log in attachment, as "mwb_log01.txt".)

Note: i had no web browser opened/active at that time.

 

So, i was wondering what is going on and launched my Firefox browser. As soon as i did that, i got 2nd MWB Premium pop-up, of same nature, but this time Firefox tried to connect and it was blocked as Trojan.

(2nd report log about firefox in attachment, as "mwb_log02.txt".)

 

Some Google-Fu and i have same issue as this user here in MWB forums,

topic:

 

With a diff, that for me, only 2 such pop-ups appeared, thus far.

 

Did manual scan after that and MWB Premium tells that 0 was found and system is clean.

Should i be worried about those two Trojan pop-ups?

 

--

Thanks in advance,

Aeacus

mwb_log01.txt mwb_log02.txt

[Porthos]

@Aeacus Update Malwarebytes manually and see if it is still happening.

[Aeacus]

2 minutes ago, Porthos said:

@Aeacus Update Malwarebytes manually and see if it is still happening.

Thanks for reply.

 

Did try the manual "Check for updates" and update was found, after which update was downloaded and installed successfully.

 

Thus far, i haven't gotten any other pop-ups of blocked outbound connections.
I guess those two pop-ups were a fluke? Whereby, somehow, MWB Premium failed to update itself and had old/obsolete detection rules still in use? 🤔

[Porthos]

Just now, Aeacus said:

MWB Premium failed to update itself and had old/obsolete detection rules still in use?

Malwarebytes checks for updates hourly by default.

The corrected database was just released.

[Aeacus]

2 minutes ago, Porthos said:

The corrected database was just released.

Oh, so it was (old) database error. Makes sense.

If so, i guess this topic has concluded and can be closed/archived. If my issue happens to reappear, i can always pop a PM to mod/admin for reopen my topic.

 

Thanks and take care. 🙂

 

[Porthos]

Since this issue is resolved the topic will now be closed to prevent others from posting here.

If you need assistance please start your own new topic and someone will be happy to assist you.

Thanks