ABUSE.MOM
THREAT REPORT

IP Threat Report
3.128.197.141

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-26 23:51:55
First seen: 2026-05-21 19:08:26
Last seen: 2026-05-24 09:42:21
100

⛔ Verdict: BLOCK

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

BOT_UABURSTUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 6/2sAbnormally fast request rate — automated scanning+35
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 100
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-05-21 19:08:26
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 6/2s (+35), UA bot: python (+40), UA changed (+25)
2026-05-24 09:42:21
Last malicious request observed
Total score reached: 100/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

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

Recommendations

Actions taken & recommended

  • IP 3.128.197.141 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.128.197.141.

🤖 Bot Detection

Address UA spoofing from 3.128.197.141: 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
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

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

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 3.128.197.141 has been traced to Dublin, United States, operating on the network of Amazon.com, Inc.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 101 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~50.5 requests per day. 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. United States currently accounts for 130 blocked IPs in our database, making it a significant source of malicious traffic. A score of 100/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.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS16509

15.220.152.241 (320)18.219.106.176 (315)15.220.169.114 (280)108.136.131.13 (265)54.206.58.169 (263)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.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: