ABUSE.MOM
THREAT REPORT

IP Threat Report
47.128.30.185

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:18:45
First seen: 2026-03-20 15:00:06
Last seen: 2026-05-30 06:17:11
110

⛔ Verdict: BLOCK

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

BOT_UABURSTREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 42/2sAbnormally fast request rate — automated scanning+35
Burst 46/2sAbnormally fast request rate — automated scanning+35
Burst 70/10sAbnormally fast request rate — automated scanning+35
Burst 76/10sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 24 req / 10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA bot: spiderKnown bot/crawler User-Agent detected+40
Σ = 260
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-20 15:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 42/2s (+35), Burst 46/2s (+35), Burst 70/10s (+35)
2026-05-30 06:17:11
Last malicious request observed
Total score reached: 110/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.30.185 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.30.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Traffic Flood Defense

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

🤖 Bot Detection

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

07

Neighbors in 47.128.30.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
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org

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

10

Threat Analysis

47.128.30.185 has been assigned a threat score of 110/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

47.128.30.185 is registered in Singapore, Singapore, operating on the network of Amazon Technologies Inc. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 776 malicious requests from this address across a 70-day span, reflecting a sustained attack cadence of ~11.1 requests per day. 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 Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Singapore currently accounts for 152 blocked IPs in our database, making it a significant source of malicious traffic. A score of 110/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 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

💡 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.

💡 IoT Device Compromise Patterns

Internet of Things devices are prime targets for botnet recruitment due to weak default credentials, infrequent updates, and always-on connectivity. Compromised IoT devices generate persistent scanning and attack traffic without their owners knowledge.

🔍 Check Any IP Address

Share this report: