ABUSE.MOM
THREAT REPORT

IP Threat Report
83.171.224.205

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 03:19:19
First seen: 2026-09-15 21:24:33
Last seen: 2026-09-20 02:14:07
95

⛔ Verdict: BLOCK

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

BURSTRATIO_404
01

Geolocation & Classification

IP Address
83.171.224.205
Type
Residential
Country
🇺🇸 United States
City
Secaucus
ISP
Baykov Ilya Sergeevich
Organization
Baykov Ilya Sergeevich
Autonomous System
AS41745 Baykov Ilya Sergeevich
Hit Count
305
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 12/10sAbnormally fast request rate — automated scanning+35
Burst 12/2sAbnormally fast request rate — automated scanning+35
Σ = 95
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-09-15 21:24:33
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 12/10s (+35), Burst 12/2s (+35)
2026-09-20 02:14:07
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Baykov Ilya Sergeevich
AS41745 · 🇺🇸 United States

We have detected 8 malicious IPs from this autonomous system.

View all IPs from AS41745 →
06

Recommendations

Actions taken & recommended

  • IP 83.171.224.205 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 83.171.224.205: 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 83.171.224.205.

09

Blacklist Status (DNSBL)

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

✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

83.171.224.205 has been assigned a threat score of 95/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 EnumerationRequest Flooding

📊 Threat Analysis

Network traffic from 83.171.224.205, located in Secaucus, United States, operating on the network of Baykov Ilya Sergeevich, has been classified as malicious by our automated threat scoring engine. The address has been active for 4 days in our monitoring system, producing 305 flagged requests at a rate of ~76.3/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 36,308 blocked IPs in our database, making it a major source of malicious traffic. A score of 95/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS41745

93.177.116.84 (105)138.124.15.176 (103)213.21.240.37 (95)192.145.30.123 (93)46.21.80.7 (90)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.

💡 VPN Exit Node Reputation

VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.

🔍 Check Any IP Address

Share this report: