ABUSE.MOM
THREAT REPORT

IP Threat Report
138.197.131.132

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 00:46:58
First seen: 2026-07-23 04:45:33
Last seen: 2026-07-26 04:03:57
173

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODUA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
138.197.131.132
Type
Hosting
Country
🇨🇦 Canada
City
Toronto
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
143
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 11/10sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 188
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-07-23 04:45:33
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 11/10s (+35), Burst 6/2s (+35), Danger medium hits: 2 (+20)
2026-07-26 04:03:57
Last malicious request observed
Total score reached: 173/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇨🇦 Canada
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

IP 138.197.131.132 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 Bot Detection

Address UA spoofing from 138.197.131.132: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

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
psbl.surriel.com
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
bl.spamcop.net

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

10

Threat Analysis

138.197.131.132 has been assigned a threat score of 173/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 138.197.131.132 has been traced to Toronto, Canada, operating on the network of DigitalOcean, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 2-day observation window, we recorded 143 hostile requests from this IP — roughly 71.5 per day on average. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With a threat score of 173/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 Canada

165.22.229.47 (158)165.22.224.166 (120)138.197.136.19 (120)159.203.39.113 (120)134.122.32.6 (120)View all →

🏢 Same network: AS14061

157.230.45.147 (265)152.42.180.126 (263)137.184.112.33 (255)68.183.5.181 (248)152.42.242.135 (230)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 GDPR and Threat Intelligence

Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.

🔍 Check Any IP Address

Share this report: