ABUSE.MOM
THREAT REPORT

IP Threat Report
57.141.22.26

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 15:54:57
First seen: 2026-09-11 00:34:54
Last seen: 2026-09-13 01:12:18
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
57.141.22.26
Type
Hosting
Country
🇺🇸 United States
City
Miami
ISP
Facebook, Inc.
Organization
Facebook, Inc
Autonomous System
AS32934 Facebook, Inc.
Hit Count
75
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
Σ = 60
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-09-11 00:34:54
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger strong hits: 1 (+25), Foreign referer (+10)
2026-09-13 01:12:18
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Facebook, Inc.
AS32934 · 🇺🇸 United States

We have detected 70 malicious IPs from this autonomous system.

View all IPs from AS32934 →
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

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

07

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

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

10

Threat Analysis

57.141.22.26 has been assigned a threat score of 60/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 57.141.22.26 to malicious activity originating from Miami, United States, operating on the network of Facebook, Inc.. The address has been under observation since its initial detection. Over a period of 2 days, this IP generated 75 malicious requests, averaging approximately 37.5 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 36,334 flagged addresses, United States represents a major presence in our threat database. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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

69.171.242.113 (145)31.13.127.87 (135)31.13.127.41 (135)69.171.242.4 (135)31.13.127.18 (135)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 CORS Misconfiguration Exploitation

Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.

🔍 Check Any IP Address

Share this report: