Jump to content

Port 445 - Inbound connections from strange IPs?


Go to solution Solved by AdvancedSetup,

Recommended Posts

Hello! I've been recently getting inbound connections blocked by Malwarebytes from strange IPs. I have run a complete scan with rootkit scan enabled and can't seem to find anything. What are these? I've attached 2 logs below.

 

Edited by AdvancedSetup
logs removed per request
Link to post
Share on other sites
  • Root Admin

Hello @carenthusiast

There isn't too much one can do with Inbound IP, but Malwarebytes is doing it's job to block them. Basically there are systems out there that attempt to probe computers looking for weaknesses. They normally go away on their own within a few hours up to a few days.

If you like we can do some scans on your system to make sure there are no infections, but otherwise Malwarebytes is doing it's job to block them.

Thank you

 

Link to post
Share on other sites
  • Root Admin

Scans not Scams 🙂

 

Please download Farbar Recovery Scan Tool and save it to your desktop.

Note: You need to run the version compatible with your system.
You can check here if you're not sure if your computer is 32-bit or 64-bit

  • Double-click to run it. When the tool opens click Yes to disclaimer.
  • Press the Scan button.
  • It will make a log (FRST.txt) in the same directory the tool is run. Please attach it to your reply.
  • The first time the tool is run, it also makes another log (Addition.txt). Please attach it to your reply as well.

Thank you

 

 

Link to post
Share on other sites
  • Root Admin
  • Solution

ATTENTION: System Restore is disabled (Total:110.22 GB) (Free:25.47 GB) (23%)

Please enable System Protection and create a new Restore Point

https://www.thewindowsclub.com/system-restore-disabled-turn-on-system-restore-windows

 

It looks like you had Avast antivirus installed at one point. Was that removed on purpose? Did you want me to provide you with a clean up script to remove all the old Avast entries?

Firefox has some type of policy on it. We can remove that for you with a clean up script

You have a Firewall and an NVIDIA issue in the Event Logs too

Error: (11/18/2020 07:15:04 PM) (Source: Steam Client Service) (EventID: 1) (User: )
Description: Error: Failed to add firewall exception for C:\Program Files (x86)\Steam\bin\cef\cef.win7\steamwebhelper.exe

Error: (11/18/2020 07:13:58 PM) (Source: NVIDIA OpenGL Driver) (EventID: 1) (User: )
Description: The GPU has been disconnected and this application may become unresponsive.

Error code: 10
 (pid=4760 tid=8472 setup.exe 32bit)

Visit http://www.nvidia.com/page/support.html for more information.

 

Malwarebytes looks like it could also use a clean removal and re-install

Please let me know about the Avast and enable your System Protection and create a new Restore Point please.

Thanks

 

Link to post
Share on other sites

Hello! I installed Avast just for a quick scan and then uninstalled it, nothing unusual I'd guess. Any reason to re-install Malwarebytes?

 

I've enabled System Restoration for both storage units now, thanks!

 

As for that Nvidia/Steam error, I think it was due to a game I installed. It's functional though.

 

Was there any sign of Malware in the logs at all?

Link to post
Share on other sites
  • Root Admin

There were no real signs of any infection in the logs. The logs in general look pretty good.

There is some indication of an issue with Malwarebytes, but it could have been a one-off fluke. Doing a clean reinstall depends on how long Malwarebytes has been installed and if you've had any signs of issues with the program or this was a fluke. Doing a clean removal and reinstall wouldn't hurt though.

This is a generic clean up script that also cleans all the temp, checks and verifies all the Windows operating system files. Clears old Windows update cache files, etc. Please see the NOTES below and read this entire post before proceeding.

 

Please download the attached fixlist.txt file and save it to the Desktop or location where you ran FRST from.
NOTE. It's important that both files, FRST or FRST64, and fixlist.txt are in the same location or the fix will not work.

Please make sure you disable any real-time antivirus or security software before running this script. Once completed making sure you re-enable it.

NOTICE: This script was written specifically for this user, for use on this particular machine. Running this on another machine may cause damage to your operating system that cannot be undone.

Run FRST or FRST64 and press the Fix button just once and wait.
If the tool needs a restart please make sure you let the system restart normally and let the tool complete its run after restart.
The tool will make a log on the Desktop (Fixlog.txt) or wherever you ran FRST from. Please attach or post it to your next reply.

Note: If the tool warned you about an outdated version please download and run the updated version.

NOTE-1:  This fix will run a scan to check that all Microsoft operating system files are valid and not corrupt and attempt to correct any invalid files. It will also run a disk check on the restart to ensure disk integrity. Depending on the speed of your computer this fix may take 30 minutes or more.

NOTE-2: As part of this fix all temporary files will be removed. If you have any open web pages that have not been bookmarked please make sure you bookmark them now as all open applications will be automatically closed. Also, make sure you know the passwords for all websites as cookies will also be removed. The use of an external password manager is highly recommended instead of using your browser to store passwords.

The following directories are emptied:

  • Windows Temp
  • Users Temp folders
  • Edge, IE, FF, Chrome and Opera caches, HTML5 storages, Cookies and History
  • Recently opened files cache
  • Flash Player cache
  • Java cache
  • Steam HTML cache
  • Explorer thumbnail and icon cache
  • BITS transfer queue (qmgr*.dat files)
  • Recycle Bin

Important: items are permanently deleted. They are not moved to quarantine. If you have any questions or concerns please ask before running this fix.

The system will be rebooted after the fix has run.

fixlist.txt

Thanks

 

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.