AbuseIPDB » 136.158.33.54
IP info including ISP, Usage Type, and Location provided by IPInfo. Updated weekly.
Top Reporter Countries (Last 60 Days)
Example preview
Report Categories (Last 60 Days)
Example previewIP Abuse Reports for 136.158.33.54:
This IP address has been reported a total of 10 times from 9 distinct sources. 136.158.33.54 was first reported on , and the most recent report was . In the last 60 days, the top reporter locations were: United States of America with 2 reports; Germany with 1 report; Japan with 1 report. The most common categories in these recent reports were: Port Scan 4 times; Hacking 2 times.
| Reporter | IoA Timestamp (UTC) | Comment | Categories | |
|---|---|---|---|---|
| Anonymous |
suricata IPS/IDS detection, ruleset ET SCAN Potential SSH Scan
|
Port Scan | ||
| 🇺🇸 RAP |
2026-09-12 17:18:08 UTC Unauthorized activity to TCP port 23. Telnet
|
Port Scan | ||
| Anonymous |
denied traffic to a honeypot network. destination port 22.
|
Port Scan Hacking | ||
| 🇺🇸 cybsecaoccol |
unauthorized connection or malicious port scan attempted on tcp port - corp
|
Port Scan Hacking | ||
| 🇩🇪 filstal.org |
|
Bad Web Bot Web App Attack | ||
| 🇧🇷 hostseries |
Trigger: LF_DISTATTACK
|
Brute-Force | ||
| 🇩🇪 seller_service |
php WP PHPmyadamin ABUSE blocked for 12h
|
Web App Attack | ||
| 🇺🇸 etu brutus |
21/2/21@21:43:40: FAIL: Alarm-Intrusion address from=136.158.33.54
...
|
Hacking Brute-Force IoT Targeted | ||
| 🇩🇪 SCHAPPY |
Wordpress attack
|
Web App Attack | ||
| 🇩🇪 seller_service |
php WP PHPmyadamin ABUSE blocked for 12h
|
Web App Attack |
Showing 1 to 10 of 10 reports
Think this IP has been falsely reported? You may request to have the associated reports reviewed and removed. Request Takedown 🚩