ABUSE.MOM
THREAT REPORT

IP Threat Report
47.128.120.184

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 08:36:46
First seen: 2026-03-13 21:00:05
Last seen: 2026-04-12 00:00:10
120

⛔ Verdict: BLOCK

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

BOT_UABURSTREFERERRATIO_404
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: spiderKnown bot/crawler User-Agent detected+40
Burst: 28 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 28 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Σ = 210
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-03-13 21:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: spider (+40), Burst: 28 req / 2s (+35), Burst: 28 req / 10s (+35)
2026-04-12 00:00:10
Last malicious request observed
Total score reached: 120/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 47.128.120.184 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 47.128.120.0/24
  • 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 47.128.120.184: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🌊 Traffic Flood Defense

IP 47.128.120.184 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🔎 Path Enumeration Protection

Block scanning from 47.128.120.184: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 47.128.120.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

47.128.120.184 has been assigned a threat score of 120/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent AnomalyRequest FloodingPath Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 47.128.120.184, geolocated to Singapore, Singapore, operating on the network of Amazon Technologies Inc, as a source of suspicious network activity. The address has been active for 29 days in our monitoring system, producing 7 flagged requests at a rate of ~0.2/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Singapore currently accounts for 152 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 120/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 Singapore

85.203.23.12 (340)85.203.23.31 (330)84.17.39.195 (325)192.166.246.30 (325)85.203.21.101 (320)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.

💡 DNS-Based Threat Detection

Monitoring DNS queries reveals malicious activity including command-and-control communication, data exfiltration through DNS tunneling, and connections to known malicious domains. DNS is often the first indicator of compromise in network forensics.

🔍 Check Any IP Address

Share this report: