ABUSE.MOM
THREAT REPORT

IP Threat Report
193.37.32.69

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 09:38:57
First seen: 2026-02-20 08:40:05
Last seen: 2026-03-20 01:00:08
195

⛔ Verdict: BLOCK

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

BOT_UAUA_CHANGEDDANGER_PATHBURST
01

Geolocation & Classification

IP Address
193.37.32.69
Type
VPN/Proxy
Country
🇸🇬 Singapore
City
Singapore
ISP
F.N.S. HOLDINGS LIMITED
Organization
VPN Consumer Singapore, Republic of Singapore
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 48High-risk paths: shells, RCE vectors, exploits+100
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 38 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 235
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-02-20 08:40:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: Go-http-client (+40), UA changed for same IP (+25), Danger strong hits: 48 (+100)
2026-03-20 01:00:08
Last malicious request observed
Total score reached: 195/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

F.N.S. HOLDINGS LIMITED
AS206092 · 🇸🇬 Singapore
06

Recommendations

Actions taken & recommended

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

🤖 User-Agent Anomaly Defense

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

🌊 Flood / DDoS Mitigation

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

07

Neighbors in 193.37.32.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
zen.spamhaus.org
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

193.37.32.69 has been assigned a threat score of 195/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:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

The address 193.37.32.69 originates from Singapore, Singapore, operating on the network of F.N.S. HOLDINGS LIMITED. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 2 malicious requests from this address across a 27-day span, reflecting a sustained attack cadence of ~0.1 requests per day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. Two attack patterns were identified (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Singapore currently accounts for 158 blocked IPs in our database, making it a significant source of malicious traffic. At 195/100, this is an extremely high-risk address. All traffic should be considered hostile.

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 Singapore

85.203.23.12 (340)85.203.23.31 (330)84.17.39.195 (325)192.166.246.30 (325)85.203.21.101 (320)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.

💡 Multi-Factor Authentication Importance

MFA dramatically reduces the effectiveness of credential-based attacks. Even when passwords are compromised through phishing or data breaches, the additional authentication factor prevents unauthorized access in the vast majority of cases.

🔍 Check Any IP Address

Share this report: