ABUSE.MOM
THREAT REPORT

IP Threat Report
104.243.245.4

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:22:20
First seen: 2026-03-03 14:00:06
Last seen: 2026-03-03 14: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: 2.

UA_CHANGEDDANGER_PATHBURST
01

Geolocation & Classification

IP Address
104.243.245.4
Type
Residential
Country
🇲🇽 Mexico
City
Mexico City
ISP
Ipxo LLC
Organization
Unknown
Autonomous System
AS396356 Latitude.sh
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 461High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 959Medium-risk: admin panels, config files+60
Burst: 11 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 38 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-03 14: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: 461 (+100), Danger medium hits: 959 (+60)
2026-03-03 14: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

Ipxo LLC
AS396356 · 🇲🇽 Mexico
06

Recommendations

Actions taken & recommended

  • IP 104.243.245.4 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 104.243.245.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 104.243.245.4 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🌊 Traffic Flood Defense

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

07

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

104.243.245.4 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

Network traffic from 104.243.245.4, located in Mexico City, Mexico, operating on the network of Ipxo LLC, has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Two attack patterns were identified (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. At 255/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇲🇽 Top threats from Mexico

104.243.245.7 (255)104.243.245.6 (205)View all →

🏢 Same network: AS396356

173.239.224.82 (320)185.223.152.42 (320)185.223.152.45 (320)185.223.152.53 (305)45.132.115.4 (305)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Ransomware-as-a-Service Economy

The RaaS model allows technically unskilled criminals to deploy sophisticated ransomware through affiliate programs. Operators provide the malware, infrastructure, and negotiation services, taking a percentage of ransom payments from their affiliates.

🔍 Check Any IP Address

Share this report: