ABUSE.MOM
THREAT REPORT

IP Threat Report
209.87.169.148

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 10:27:03
First seen: 2026-02-21 18:50:04
Last seen: 2026-04-21 08:00:23
255

⛔ Verdict: BLOCK

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

UA_SUSDANGER_PATHRATIO_404UA_CHANGEDBURST
01

Geolocation & Classification

IP Address
209.87.169.148
Type
Residential
Country
🇺🇸 United States
City
Jersey City
ISP
Active Data
Organization
Unknown
Autonomous System
AS62240 Clouvider
Hit Count
11
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 378High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 970Medium-risk: admin panels, config files+60
Burst: 22 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 76 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 70 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 102High-risk paths: shells, RCE vectors, exploits+100
Burst: 68 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 127High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 50Medium-risk: admin panels, config files+60
Burst: 72 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 19 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 64 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 865
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-21 18:50:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA suspicious (short/empty) (+15), Danger strong hits: 1 (+25), Danger medium hits: 1 (+10)
2026-04-21 08:00:23
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

Active Data
AS62240 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

Block scanning from 209.87.169.148: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

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

07

Neighbors in 209.87.169.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
Spamhaus ZEN

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

10

Threat Analysis

209.87.169.148 has been assigned a threat score of 255/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

IP address 209.87.169.148 has been traced to Jersey City, United States, operating on the network of Active Data. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 58 days in our monitoring system, producing 11 flagged requests at a rate of ~0.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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. United States currently accounts for 212 blocked IPs in our database, making it a significant source of malicious traffic. A score of 255/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS62240

92.119.36.49 (330)45.147.244.27 (313)98.159.37.212 (305)92.119.36.41 (305)92.119.36.92 (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.

💡 Remote Code Execution (RCE)

RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.

🔍 Check Any IP Address

Share this report: