ABUSE.MOM
THREAT REPORT

IP Threat Report
47.128.120.195

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 05:01:13
First seen: 2026-04-10 00:00:07
Last seen: 2026-05-24 09:51:19
80

⛔ Verdict: BLOCK

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

BOT_UABURSTREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 10/10sAbnormally fast request rate — automated scanning+35
Burst 9/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Foreign referer seenReferer from unrelated external domain+10
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA bot: spiderKnown bot/crawler User-Agent detected+40
Σ = 170
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-04-10 00:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 10/10s (+35), Burst 9/2s (+35), Foreign referer (+10)
2026-05-24 09:51:19
Last malicious request observed
Total score reached: 80/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.195 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

🌊 Flood / DDoS Mitigation

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

🤖 User-Agent Anomaly Defense

IP 47.128.120.195 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

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

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

10

Threat Analysis

47.128.120.195 has been assigned a threat score of 80/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

The address 47.128.120.195 originates from Singapore, Singapore, operating on the network of Amazon Technologies Inc. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 506 malicious requests from this address across a 44-day span, reflecting a sustained attack cadence of ~11.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. Singapore currently accounts for 152 blocked IPs in our database, making it a significant source of malicious traffic. At 80/100, this IP warrants immediate defensive action.

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.

💡 Dark Web Intelligence Gathering

Monitoring dark web forums and marketplaces provides advance warning of planned attacks, leaked credentials, and compromised data. This intelligence feeds into proactive defense measures before attacks reach their targets.

🔍 Check Any IP Address

Share this report: