ABUSE.MOM
THREAT REPORT

IP Threat Report
3.145.165.243

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 08:58:35
First seen: 2026-09-20 06:33:30
Last seen: 2026-09-27 00:11:00
145

⛔ Verdict: BLOCK

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

BOT_UABURSTREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
3.145.165.243
Type
Hosting
Country
🇺🇸 United States
City
Columbus
ISP
Amazon.com, Inc.
Organization
AWS EC2 (us-east-2)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
176
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 14/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 145
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-09-20 06:33:30
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 12/2s (+35), Burst 14/10s (+35), Foreign referer (+10)
2026-09-27 00:11:00
Last malicious request observed
Total score reached: 145/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com, Inc.
AS16509 · 🇺🇸 United States

We have detected 1328 malicious IPs from this autonomous system.

View all IPs from AS16509 →
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

🤖 User-Agent Anomaly Defense

IP 3.145.165.243 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

3.145.165.243 has been assigned a threat score of 145/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 3.145.165.243 to malicious activity originating from Columbus, United States, operating on the network of Amazon.com, Inc.. The address has been under observation since its initial detection. During its 6-day observation window, we recorded 176 hostile requests from this IP — roughly 29.3 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 36,231 flagged addresses, United States represents a major presence in our threat database. A score of 145/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 United States

104.28.246.115 (350)104.28.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS16509

3.26.255.172 (308)3.26.98.5 (308)35.180.172.183 (298)3.129.218.216 (288)18.191.74.68 (288)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.

💡 False Positive Management

False positives erode trust in security systems and waste analyst resources. Effective management requires feedback loops, allowlisting mechanisms, contextual analysis, and regular tuning of detection rules based on operational experience.

🔍 Check Any IP Address

Share this report: