ABUSE.MOM
THREAT REPORT

IP Threat Report
64.144.6.133

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:30:44
First seen: 2026-05-07 19:00:05
Last seen: 2026-05-07 19:00:05
90

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
64.144.6.133
Type
Hosting
Country
🇺🇸 United States
City
Denver
ISP
GTT Americas
Organization
Unknown
Autonomous System
AS30058 FDCservers.net
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: crawlerKnown bot/crawler User-Agent detected+40
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Σ = 90
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-05-07 19:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: crawler (+40), Danger strong hits: 1 (+25), 404 ratio >= 60% (+25)
2026-05-07 19:00:05
Last malicious request observed
Total score reached: 90/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

GTT Americas
AS30058 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 64.144.6.133 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

🤖 User-Agent Anomaly Defense

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

🔎 Directory Scan Defense

IP 64.144.6.133 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (1)
PortServiceRiskDescription
60000UnknownLowService on port 60000
Hostnames: 64-144-6-133.client.dsl.net
PTR: 64-144-6-133.client.dsl.net

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

64.144.6.133 has been assigned a threat score of 90/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 AnomalyPath Enumeration

📊 Threat Analysis

The address 64.144.6.133 originates from Denver, United States, operating on the network of GTT Americas. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. A score of 90/100 places this address in the top tier of severity. Block and investigate any historical connections.

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

View all →

🏢 Same network: AS30058

64.139.50.130 (105)50.7.230.162 (105)67.159.24.34 (80)50.7.124.7 (70)151.244.0.40 (70)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.

💡 Server-Side Template Injection

SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.

🔍 Check Any IP Address

Share this report: