ABUSE.MOM
THREAT REPORT

IP Threat Report
179.89.207.114

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 13:38:52
First seen: 2026-03-09 23:00:06
Last seen: 2026-03-09 23: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: 2.

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
179.89.207.114
Type
Residential
Country
🇧🇷 Brazil
City
Florianópolis
ISP
Vivo
Organization
TELEF�NICA BRASIL S.A
Autonomous System
AS26599 TELEFÔNICA BRASIL S.A
Hit Count
2
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-09 23:00:06
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-09 23: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

Vivo
AS26599 · 🇧🇷 Brazil
06

Recommendations

Actions taken & recommended

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

179.89.207.114 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 179.89.207.114, located in Florianópolis, Brazil, operating on the network of Vivo, 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. Brazil currently accounts for 148 blocked IPs in our database, making it a significant source of malicious traffic. At 103/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 Brazil

173.245.211.6 (293)20.206.78.203 (283)20.197.194.128 (280)20.197.233.108 (280)20.226.83.230 (280)View all →

🏢 Same network: AS26599

187.91.168.111 (245)177.171.115.35 (128)177.62.239.78 (103)179.87.167.164 (103)177.162.25.88 (103)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.

💡 Content Security Policy Implementation

Content Security Policy headers instruct browsers to restrict resource loading, mitigating XSS and data injection attacks. Properly configured CSP policies prevent inline script execution, restrict iframe embedding, and control which domains can serve content.

🔍 Check Any IP Address

Share this report: