ABUSE.MOM
THREAT REPORT

IP Threat Report
3.107.235.137

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 10:41:56
First seen: 2026-07-24 11:42:49
Last seen: 2026-07-26 04:02:03
238

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
3.107.235.137
Type
Hosting
Country
🇦🇺 Australia
City
Sydney
ISP
Amazon Technologies Inc.
Organization
AWS EC2 (ap-southeast-2)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
61
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 10/2sAbnormally fast request rate — automated scanning+35
Burst 35/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 160Medium-risk: admin panels, config files+60
Danger medium hits: 80Medium-risk: admin panels, config files+60
Danger strong hits: 1480High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 740High-risk paths: shells, RCE vectors, exploits+100
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 398
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-24 11:42:49
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 10/2s (+35), Burst 35/10s (+35), Danger medium hits: 160 (+60)
2026-07-26 04:02:03
Last malicious request observed
Total score reached: 238/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon Technologies Inc.
AS16509 · 🇦🇺 Australia
06

Recommendations

Actions taken & recommended

  • IP 3.107.235.137 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 3.107.235.137 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

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

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

10

Threat Analysis

3.107.235.137 has been assigned a threat score of 238/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 Flooding

📊 Threat Analysis

Network traffic from 3.107.235.137, located in Sydney, Australia, operating on the network of Amazon Technologies Inc., has been classified as malicious by our automated threat scoring engine. Our sensors captured 61 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~61 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. With 101 flagged addresses, Australia represents a significant presence in our threat database. With a threat score of 238/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 Australia

34.129.231.194 (295)34.129.253.231 (295)20.5.80.84 (280)20.53.249.250 (280)20.5.216.136 (280)View all →

🏢 Same network: AS16509

35.180.172.183 (298)3.129.218.216 (288)18.191.74.68 (288)3.72.250.64 (280)15.220.152.126 (280)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.

💡 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: