ABUSE.MOM
THREAT REPORT

IP Threat Report
200.139.93.67

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 02:15:53
First seen: 2026-08-25 02:19:26
Last seen: 2026-08-30 01:00:17
140

⛔ Verdict: BLOCK

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

DANGER_PATHREFERER
01

Geolocation & Classification

IP Address
200.139.93.67
Type
Residential
Country
🇧🇷 Brazil
City
Belo Horizonte
ISP
Vivo
Organization
TELEF�NICA BRASIL S.A
Autonomous System
AS18881 TELEFÔNICA BRASIL S.A
Hit Count
147
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
Σ = 140
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-08-25 02:19:26
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 3 (+30), Danger strong hits: 4 (+100), Foreign referer (+10)
2026-08-30 01:00:17
Last malicious request observed
Total score reached: 140/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Vivo
AS18881 · 🇧🇷 Brazil
06

Recommendations

Actions taken & recommended

  • IP 200.139.93.67 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 200.139.93.67 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.

✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

200.139.93.67 has been assigned a threat score of 140/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

📊 Threat Analysis

Threat intelligence analysis has linked 200.139.93.67 to malicious activity originating from Belo Horizonte, Brazil, operating on the network of Vivo. The address has been under observation since its initial detection. Our sensors captured 147 malicious requests from this address across a 4-day span, reflecting a sustained attack cadence of ~36.8 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. With 103 flagged addresses, Brazil represents a significant presence in our threat database. With a threat score of 140/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

34.95.200.255 (320)107.149.152.45 (308)34.95.148.192 (298)35.247.218.13 (298)35.247.222.75 (295)View all →

🏢 Same network: AS18881

189.58.139.223 (140)191.32.163.102 (60)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 SSH Brute Force Defense

SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.

🔍 Check Any IP Address

Share this report: