ABUSE.MOM
THREAT REPORT

IP Threat Report
18.136.36.22

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-08 17:35:58
First seen: 2026-08-08 04:18:30
Last seen: 2026-08-09 04:12:46
75

⛔ Verdict: BLOCK

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

BOT_UARATIO_404REFERER
01

Geolocation & Classification

IP Address
18.136.36.22
Type
Hosting
Country
🇸🇬 Singapore
City
Singapore
ISP
Amazon Technologies Inc.
Organization
AWS EC2 (ap-southeast-1)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
29
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Foreign refererReferer from unrelated external domain+10
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Σ = 75
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-08 04:18:30
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Foreign referer (+10), UA bot: Go-http-client (+40)
2026-08-09 04:12:46
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 Technologies Inc.
AS16509 · 🇸🇬 Singapore
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 18.136.36.22 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 User-Agent Anomaly Defense

IP 18.136.36.22 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
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 18.136.36.22, geolocated to Singapore, Singapore, operating on the network of Amazon Technologies Inc., as a source of suspicious network activity. During its 1-day observation window, we recorded 29 hostile requests from this IP — roughly 29 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 Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With 115 flagged addresses, Singapore represents a significant presence in our threat database. 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 Singapore

85.203.23.12 (340)103.167.150.231 (340)62.146.238.136 (340)85.203.23.31 (330)192.166.246.30 (325)View all →

🏢 Same network: AS16509

35.180.172.183 (298)3.129.218.216 (288)18.191.74.68 (288)34.244.9.175 (288)51.44.13.36 (288)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Business Email Compromise Tactics

BEC attacks use compromised or spoofed executive email accounts to request fraudulent wire transfers or sensitive data. These attacks cause billions in annual losses and rely on social engineering rather than technical exploitation.

🔍 Check Any IP Address

Share this report: