Thank you. Yes, I can understand how the whole situation must be intensely irritating. Happily, I'm still in a state of innocence as I only installed MBAM Pro a few hours ago and haven't yet discovered the log you mention. I now begin to think that life may prove less stressful if I don't discover it since, as you've shown, there's not much to be done about those pesky Chinamen anyway.
Hello friend!!
I was a member on IObit forum which has a Chinese Company (IObit 360.) We had a disagreement which lead to some very bad exchanges. This is how they retaliate. No one wants to believe me and I have stopped trying to expose their behavior on facebook. I decided to post here on BleepingComputer hoping to draw some attention here to the way they behave. I have been banned deleted and cussed out for posting these things, so I have to be very cautious.
Here is a MBAM log of their attempted attacks to find a open port for what I believe is for malicious reasons.
Thank you my friend for your post.
I'm very well protected from these attacks and have my OS backed up in three different places. When I see these attacks, I just change my IP address. I'm tired of trying to get some one to stop this as it seems hopeless. It seems that even Home Land Security could care less as I have written them a personal letter about this behavior. I mainly want to warn people and tell them their PC could be compromised by these Chinese hackers. If I can accomplish that, I will feel good about this. This logs shows that I allowed them to try for awhile, but changed my IP address and that stopped them. I think you can see this thread on Google (Blocked Chinese IP's) and that makes me very happy. PS Installing MBAM Pro is a very wise decision!
03:01:38 Owner MESSAGE Scheduled update executed successfully
03:01:38 Owner MESSAGE IP Protection stopped
03:01:54 Owner MESSAGE Database updated successfully
03:02:04 Owner MESSAGE IP Protection started successfully
04:34:25 Owner MESSAGE Protection started successfully
04:34:30 Owner MESSAGE IP Protection started successfully
08:01:37 Owner MESSAGE IP Protection stopped
08:01:37 Owner MESSAGE Scheduled update executed successfully
08:01:46 Owner MESSAGE Database updated successfully
08:01:53 Owner MESSAGE IP Protection started successfully
10:09:07 Owner MESSAGE Protection started successfully
10:09:13 Owner MESSAGE IP Protection started successfully
11:01:37 Owner MESSAGE Scheduled update executed successfully
11:01:37 Owner MESSAGE IP Protection stopped
11:01:46 Owner MESSAGE Database updated successfully
11:01:52 Owner MESSAGE IP Protection started successfully
11:05:07 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
11:07:40 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
11:12:36 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
11:15:36 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
11:16:16 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
11:16:16 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
11:16:22 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
11:23:54 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
11:26:50 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
11:31:23 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
11:33:41 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
11:33:41 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
11:36:29 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
11:38:50 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
11:41:10 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
11:48:22 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
11:53:34 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
11:55:37 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
11:57:46 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
12:13:00 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
12:13:08 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
12:13:09 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
12:28:40 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
12:31:40 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
12:35:21 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
12:39:05 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
12:55:35 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
12:58:29 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
13:01:30 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
13:07:00 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
13:07:30 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
13:10:35 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
13:11:08 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
13:11:08 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
13:11:08 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
13:11:47 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
13:13:27 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
13:19:22 Owner IP-BLOCK 221.192.199.48 (Type: incoming)
13:19:51 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
13:21:20 Owner IP-BLOCK 221.192.199.51 (Type: incoming)
13:27:29 Owner IP-BLOCK 221.192.199.46 (Type: incoming)
13:29:37 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
13:29:37 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
13:29:38 Owner IP-BLOCK 222.186.13.212 (Type: incoming)
15:15:00 Owner MESSAGE Scheduled scan executed successfully
16:01:41 Owner MESSAGE Scheduled update executed successfully
16:01:41 Owner MESSAGE IP Protection stopped
16:01:51 Owner MESSAGE Database updated successfully
16:02:00 Owner MESSAGE IP Protection started successfully
19:00:03 Owner ERROR Scheduled update failed: WinHttpSendRequest failed with error code 12007
19:00:04 Owner MESSAGE Protection started successfully
19:00:09 Owner MESSAGE IP Protection started successfully
20:01:43 Owner MESSAGE IP Protection stopped
20:01:43 Owner MESSAGE Scheduled update executed successfully
20:01:53 Owner MESSAGE Database updated successfully
20:01:59 Owner MESSAGE IP Protection started successfully
23:01:39 Owner MESSAGE Scheduled update executed successfully
23:01:39 Owner MESSAGE IP Protection stopped
23:01:50 Owner MESSAGE Database updated successfully
23:01:57 Owner MESSAGE IP Protection started successfully