ABUSE.MOM
THREAT REPORT

IP Threat Report
47.128.39.64

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 01:26:36
First seen: 2026-07-04 11:23:51
Last seen: 2026-09-06 01:04:34
80

⛔ Verdict: BLOCK

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

BURSTRATIO_404REFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 19/10sAbnormally fast request rate — automated scanning+35
Burst 21/10sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Σ = 130
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-07-04 11:23:51
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 19/10s (+35), Burst 21/10s (+35)
2026-09-06 01:04:34
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.39.64 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.39.0/24
  • 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 47.128.39.64 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

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

07

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

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

10

Threat Analysis

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

Path EnumerationRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 47.128.39.64, geolocated to Singapore, Singapore, operating on the network of Amazon Technologies Inc, as a source of suspicious network activity. During its 63-day observation window, we recorded 1,140 hostile requests from this IP — roughly 18.1 per day on average. 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 (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Singapore currently accounts for 111 blocked IPs in our database, making it a significant source of malicious traffic. The score of 80/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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

47.128.39.6 (80)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.

💡 Memory Safety and Buffer Overflows

Buffer overflow vulnerabilities remain relevant in C/C++ applications despite decades of mitigation efforts. Modern protections like ASLR, stack canaries, and DEP reduce exploitability but determined attackers continue finding bypass techniques.

🔍 Check Any IP Address

Share this report: