ABUSE.MOM
THREAT REPORT

IP Threat Report
192.186.140.55

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:53:18
First seen: 2026-05-27 13:10:28
Last seen: 2026-05-30 08:45:37
130

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 130/100. Total malicious requests observed: 402.

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
192.186.140.55
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
402
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 6/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 5Medium-risk: admin panels, config files+50
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 130
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-05-27 13:10:28
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 6/2s (+35), Danger medium hits: 5 (+50)
2026-05-30 08:45:37
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 192.186.140.55 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 192.186.140.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 192.186.140.55: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 192.186.140.55.

07

Neighbors in 192.186.140.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

192.186.140.55 has been assigned a threat score of 130/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 192.186.140.55 to malicious activity originating from an unknown location. The address has been under observation since its initial detection. The address has been active for 2 days in our monitoring system, producing 402 flagged requests at a rate of ~201/day. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 IP Geolocation Accuracy Limitations

IP geolocation databases provide approximate locations with varying accuracy. City-level geolocation is typically 50-80% accurate, while country-level exceeds 95%. VPNs, proxies, and mobile networks further reduce reliability, making geolocation a useful but imperfect intelligence signal.

🔍 Check Any IP Address

Share this report: