ABUSE.MOM
THREAT REPORT

IP Threat Report
216.10.217.177

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 10:48:37
First seen: 2026-03-08 08:00:04
Last seen: 2026-03-19 21:00:06
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
216.10.217.177
Type
Residential
Country
🇯🇲 JM
City
Kingston
ISP
FLOW
Organization
Columbus Communications Jamaica Limited
Autonomous System
AS30689 FLOW
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
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-03-08 08:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-03-19 21:00:06
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

FLOW
AS30689 · 🇯🇲 JM
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 216.10.217.177 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

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

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

📊 Threat Analysis

Network traffic from 216.10.217.177, located in Kingston, JM, operating on the network of FLOW, has been classified as malicious by our automated threat scoring engine. During its 11-day observation window, we recorded 3 hostile requests from this IP — roughly 0.3 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. With 20 flagged addresses, JM represents a notable presence in our threat database. A score of 103/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 JM

83.219.96.25 (255)83.219.96.30 (195)207.204.64.74 (105)207.204.96.2 (103)67.230.42.146 (103)View all →

🏢 Same network: AS30689

207.204.64.74 (105)207.204.96.2 (103)67.230.42.146 (103)72.252.225.90 (103)207.204.103.39 (103)View all →
12

Security Intelligence

💡 Directory Traversal Attacks

Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.

💡 Email Authentication: SPF, DKIM, DMARC

Email authentication protocols work together to prevent spoofing. SPF validates sending servers, DKIM provides cryptographic message signing, and DMARC defines enforcement policies. Full implementation significantly reduces phishing effectiveness.

🔍 Check Any IP Address

Share this report: