ABUSE.MOM
THREAT REPORT

IP Threat Report
18.223.120.62

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 01:07:02
First seen: 2026-05-06 12:00:07
Last seen: 2026-05-16 18:00:05
75

⛔ Verdict: BLOCK

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

BOT_UABURST
01

Geolocation & Classification

IP Address
18.223.120.62
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
12
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: pythonKnown bot/crawler User-Agent detected+40
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 7 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 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-05-06 12:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: python (+40), Burst: 5 req / 2s (+35), Burst: 7 req / 2s (+35)
2026-05-16 18:00:05
Last malicious request observed
Total score reached: 75/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 18.223.120.62 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

🤖 Bot Detection

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

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

18.223.120.62 has been assigned a threat score of 75/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.

The following attack categories were identified:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

IP address 18.223.120.62 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. During its 10-day observation window, we recorded 12 hostile requests from this IP — roughly 1.2 per day on average. 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. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 130 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 75/100 places this IP in the high-risk category. Blocking at the firewall level is 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 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

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Email Authentication: SPF, DKIM, DMARC

Email authentication protocols work together to prevent spoofing. SPF validates sending servers, DKIM provides cryptographic message signing, and DMARC defines enforcement policies. Full implementation significantly reduces phishing effectiveness.

🔍 Check Any IP Address

Share this report: