ABUSE.MOM
THREAT REPORT

IP Threat Report
188.130.143.2

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:21:21
First seen: 2026-05-25 16:42:32
Last seen: 2026-05-30 07:15:47
85

⛔ Verdict: BLOCK

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

DANGER_PATHREDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
188.130.143.2
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
797
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 3Medium-risk: admin panels, config files+30
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 95
03

Observed Activity

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

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

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

04

Timeline

2026-05-25 16:42:32
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 1 (+10), Danger medium hits: 3 (+30), Foreign referer (+10)
2026-05-30 07:15:47
Last malicious request observed
Total score reached: 85/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 188.130.143.2 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 188.130.143.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

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

🤖 User-Agent Anomaly Defense

IP 188.130.143.2 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

Neighbors in 188.130.143.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
psbl.surriel.com
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org

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

10

Threat Analysis

188.130.143.2 has been assigned a threat score of 85/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

188.130.143.2 is registered in an unknown location. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 797 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~199.3 requests per day. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. At 85/100, this IP warrants immediate defensive action.

11

Related Threats

🇤🇤 Top threats from ??

View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: