ABUSE.MOM
THREAT REPORT

IP Threat Report
91.92.42.86

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 11:29:34
First seen: 2026-05-28 03:30:38
Last seen: 2026-05-30 10:39:18
265

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
91.92.42.86
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
131
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 20/10sAbnormally fast request rate — automated scanning+35
Burst 20/2sAbnormally fast request rate — automated scanning+35
Burst 34/10sAbnormally fast request rate — automated scanning+35
Burst 34/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 14Medium-risk: admin panels, config files+60
Danger medium hits: 32Medium-risk: admin panels, config files+60
Danger strong hits: 11High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 19High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 495
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-28 03:30:38
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 20/10s (+35), Burst 20/2s (+35), Burst 34/10s (+35)
2026-05-30 10:39:18
Last malicious request observed
Total score reached: 265/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

🤖 Bot Detection

Address UA spoofing from 91.92.42.86: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 91.92.42.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
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

91.92.42.86 has been assigned a threat score of 265/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

The address 91.92.42.86 originates from an unknown location. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 2-day observation window, we recorded 131 hostile requests from this IP — roughly 65.5 per day on average. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. A score of 265/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.

💡 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.

🔍 Check Any IP Address

Share this report: