ABUSE.MOM
THREAT REPORT

IP Threat Report
170.64.153.212

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 10:47:07
First seen: 2026-03-10 22:00:08
Last seen: 2026-03-10 22:00:08
198

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTREFERERMETHOD
01

Geolocation & Classification

IP Address
170.64.153.212
Type
Hosting
Country
🇦🇺 Australia
City
Sydney
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 1Medium-risk: admin panels, config files+10
Burst: 35 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 37 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 198
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-03-10 22:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 12 (+100), Danger medium hits: 1 (+10), Burst: 35 req / 2s (+35)
2026-03-10 22:00:08
Last malicious request observed
Total score reached: 198/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇦🇺 Australia
06

Recommendations

Actions taken & recommended

  • IP 170.64.153.212 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 170.64.153.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Flood / DDoS Mitigation

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

07

Neighbors in 170.64.153.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

170.64.153.212 has been assigned a threat score of 198/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

IP address 170.64.153.212 has been traced to Sydney, Australia, operating on the network of DigitalOcean, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 109 flagged addresses, Australia represents a significant presence in our threat database. A score of 198/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 Australia

20.42.209.0 (280)170.64.203.182 (280)20.213.152.227 (280)20.5.72.178 (280)4.197.33.200 (280)View all →

🏢 Same network: AS14061

129.212.237.216 (308)168.144.34.140 (295)170.64.203.182 (280)161.35.89.38 (273)64.226.94.117 (273)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.

💡 Bulletproof Hosting Ecosystem

Bulletproof hosting providers deliberately ignore abuse complaints, creating safe havens for malicious operations. These providers often operate in jurisdictions with weak cybercrime enforcement, offering services specifically marketed to criminal organizations.

🔍 Check Any IP Address

Share this report: