City: unknown
Region: unknown
Country: Czechia
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 195.133.20.193 | attack | Router logs showing dos and port scanning [DoS attack: TCP Port Scan] from source: 195.133.20.193:65533 Sunday, September 18,2022 16:33:43 Im seeing a ton of initial hits by russian based ip.. followed up after infection by what seems to be chinese methods of digging in below the os and also building a complex networking system to remove chokepoints and provide redundancy.. its happening at scale im not a direct target just a vector potentially to get into very large corporate headquarters in the area.. have found this... well remote access trojan.. in 3 businesses all major transaction business and 2 with a ton of proprietary information and designs. This is alarming and no one seems to take it as serious as it is.. in my own home ive fiddle and tested what it can do and its jaw dropping.. the level of working knowledge across sooo many systems down to the chipset instruction codes and bootloader... even using a non-storage devices rom for other purposes and moving what was originally there to else where with a working path to retrieve it so they system and hardware continues to function as it should.. just with quirks all the while making a bios flash and entirely new drive and os media useless because the malware or rogue code goes into action long before the os does. |
2022-09-20 01:21:00 |
| 195.133.206.202 | attack | Mar 5 05:53:55 [munged] sshd[18528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.133.206.202 |
2020-03-05 14:05:04 |
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 195.133.20.245
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13954
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;195.133.20.245. IN A
;; AUTHORITY SECTION:
. 583 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022061102 1800 900 604800 86400
;; Query time: 76 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 12 06:07:37 CST 2022
;; MSG SIZE rcvd: 107Host 245.20.133.195.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 245.20.133.195.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 191.223.5.21 | attackspam | Automatic report - Port Scan Attack |
2019-07-31 10:54:17 |
| 114.236.122.135 | attack | 20 attempts against mh-ssh on grain.magehost.pro |
2019-07-31 11:03:25 |
| 103.28.57.9 | attack | Jul 31 01:25:22 mail sshd\[5210\]: Failed password for invalid user shari from 103.28.57.9 port 35357 ssh2 Jul 31 01:45:22 mail sshd\[5591\]: Invalid user utnet from 103.28.57.9 port 52096 ... |
2019-07-31 10:16:29 |
| 35.192.90.67 | attackbotsspam | [WedJul3100:36:30.1204222019][:error][pid13600:tid47872649205504][client35.192.90.67:58648][client35.192.90.67]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"python-requests/"atREQUEST_HEADERS:User-Agent.[file"/etc/apache2/conf.d/modsec_rules/20_asl_useragents.conf"][line"207"][id"332039"][rev"4"][msg"Atomicorp.comWAFRules:SuspiciousUnusualUserAgent\(python-requests\).Disablethisruleifyouusepython-requests/."][severity"CRITICAL"][hostname"www.trusttechnology.ch"][uri"/"][unique_id"XUDGbkc3qLNhKQqBo9419QAAABE"][WedJul3100:36:34.6209992019][:error][pid13356:tid47872657610496][client35.192.90.67:58963][client35.192.90.67]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"python-requests/"atREQUEST_HEADERS:User-Agent.[file"/etc/apache2/conf.d/modsec_rules/20_asl_useragents.conf"][line"207"][id"332039"][rev"4"][msg"Atomicorp.comWAFRules:SuspiciousUnusualUserAgent\(python-requests\).Disablethisruleifyouusepython-requests/."][severity"CRITICAL"][hostname"www.tru |
2019-07-31 10:36:37 |
| 162.243.142.193 | attackspambots | Jul 31 04:40:34 lnxweb62 sshd[3384]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.142.193 Jul 31 04:40:34 lnxweb62 sshd[3384]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.142.193 |
2019-07-31 10:46:08 |
| 109.86.153.206 | attack | Brute force attempt |
2019-07-31 10:24:10 |
| 35.233.70.227 | attack | port scan/probe/communication attempt |
2019-07-31 10:47:27 |
| 177.38.3.87 | attack | failed_logins |
2019-07-31 11:04:25 |
| 177.44.127.199 | attack | Jul 30 17:35:43 mailman postfix/smtpd[2308]: warning: unknown[177.44.127.199]: SASL PLAIN authentication failed: authentication failure |
2019-07-31 11:01:44 |
| 175.212.62.83 | attackspambots | DATE:2019-07-31 04:02:53, IP:175.212.62.83, PORT:ssh SSH brute force auth (ermes) |
2019-07-31 10:22:19 |
| 217.128.61.137 | attackspambots | Unauthorised access (Jul 31) SRC=217.128.61.137 LEN=44 TTL=244 ID=40055 TCP DPT=445 WINDOW=1024 SYN |
2019-07-31 11:03:04 |
| 109.116.196.174 | attackbotsspam | Jul 30 19:32:19 TORMINT sshd\[17745\]: Invalid user db2admin from 109.116.196.174 Jul 30 19:32:19 TORMINT sshd\[17745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.116.196.174 Jul 30 19:32:21 TORMINT sshd\[17745\]: Failed password for invalid user db2admin from 109.116.196.174 port 38850 ssh2 ... |
2019-07-31 10:23:55 |
| 125.167.127.191 | attack | Automatic report - Port Scan Attack |
2019-07-31 10:43:03 |
| 170.239.42.164 | attackspambots | failed_logins |
2019-07-31 10:56:16 |
| 159.203.26.248 | attackbotsspam | fail2ban honeypot |
2019-07-31 10:31:43 |