ABUSE.MOM
THREAT REPORT

IP Threat Report
193.37.33.12

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:05:55
First seen: 2026-03-01 11:00:06
Last seen: 2026-03-01 11:00:06
255

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHBURST
01

Geolocation & Classification

IP Address
193.37.33.12
Type
VPN/Proxy
Country
🇺🇸 United States
City
Seattle
ISP
F.N.S. HOLDINGS LIMITED
Organization
VPN Consumer Seattle, United States of America
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 362High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 959Medium-risk: admin panels, config files+60
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 46 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 255
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-03-01 11:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 362 (+100), Danger medium hits: 959 (+60)
2026-03-01 11:00:06
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

F.N.S. HOLDINGS LIMITED
AS206092 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 193.37.33.12 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.37.33.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

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

🌊 Traffic Flood Defense

IP 193.37.33.12 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

07

Neighbors in 193.37.33.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.

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

193.37.33.12 has been assigned a threat score of 255/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

193.37.33.12 is registered in Seattle, United States, operating on the network of F.N.S. HOLDINGS LIMITED. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 151 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 255/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS206092

103.163.220.216 (340)85.203.21.101 (320)85.203.21.157 (310)85.203.21.172 (305)91.217.249.222 (305)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

🔍 Check Any IP Address

Share this report: