ABUSE.MOM
THREAT REPORT

IP Threat Report
193.36.225.64

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 02:38:19
First seen: 2026-06-12 13:58:36
Last seen: 2026-07-30 01:40:56
100

⛔ Verdict: BLOCK

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

BURSTDANGER_PATH
01

Geolocation & Classification

IP Address
193.36.225.64
Type
Unknown
Country
🇺🇸 United States
City
Los Angeles
ISP
F.N.S. HOLDINGS LIMITED
Organization
F.N.S. HOLDINGS LIMITED
Autonomous System
Unknown
Hit Count
73
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 18/10sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 80
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-06-12 13:58:36
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 18/10s (+35), Burst 8/2s (+35), Danger medium hits: 1 (+10)
2026-07-30 01:40:56
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 193.36.225.64 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 193.36.225.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 193.36.225.64.

07

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

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

10

Threat Analysis

193.36.225.64 has been assigned a threat score of 100/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 Flooding

📊 Threat Analysis

The address 193.36.225.64 originates from Los Angeles, United States, operating on the network of F.N.S. HOLDINGS LIMITED. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 47 days in our monitoring system, producing 73 flagged requests at a rate of ~1.6/day. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 151 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 100/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)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.

💡 Responsible Disclosure Ethics

Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.

🔍 Check Any IP Address

Share this report: