ABUSE.MOM
THREAT REPORT

IP Threat Report
63.135.161.123

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 01:41:08
First seen: 2026-08-30 13:23:35
Last seen: 2026-09-06 00:33:43
95

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATH
01

Geolocation & Classification

IP Address
63.135.161.123
Type
Hosting
Country
🇺🇸 United States
City
New York
ISP
F.N.S. HOLDINGS LIMITED
Organization
F.N.S. HOLDINGS LIMITED
Autonomous System
AS206092 F.N.S. HOLDINGS LIMITED
Hit Count
144
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 95
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-30 13:23:35
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 3 (+30), Danger strong hits: 1 (+25), UA bot: Go-http-client (+40)
2026-09-06 00:33:43
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

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

Recommendations

Actions taken & recommended

  • IP 63.135.161.123 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 63.135.161.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 63.135.161.123: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

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

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

10

Threat Analysis

63.135.161.123 has been assigned a threat score of 95/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

IP address 63.135.161.123 has been traced to New York, United States, operating on the network of F.N.S. HOLDINGS LIMITED. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 144 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~24 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Our records show 153 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. With a threat score of 95/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

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: AS206092

91.230.225.166 (320)185.92.25.3 (305)2.57.170.183 (305)91.230.225.140 (305)2.57.170.88 (305)View all →
12

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Zero Trust Architecture Principles

Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.

🔍 Check Any IP Address

Share this report: