ABUSE.MOM
THREAT REPORT

IP Threat Report
13.60.9.255

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 11:34:37
First seen: 2026-02-25 03:00:05
Last seen: 2026-02-25 04:00:07
170

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
13.60.9.255
Type
Hosting
Country
🇸🇪 Sweden
City
Stockholm
ISP
Amazon.com, Inc.
Organization
AWS EC2 (eu-north-1)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 240
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-02-25 03:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 12 req / 2s (+35), Burst: 12 req / 10s (+35), Danger strong hits: 8 (+100)
2026-02-25 04:00:07
Last malicious request observed
Total score reached: 170/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com, Inc.
AS16509 · 🇸🇪 Sweden
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

🔎 Directory Scan Defense

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

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

13.60.9.255 has been assigned a threat score of 170/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request FloodingPath Enumeration

📊 Threat Analysis

IP address 13.60.9.255 has been traced to Stockholm, Sweden, operating on the network of Amazon.com, Inc.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 1 days, this IP generated 2 malicious requests, averaging approximately 2 requests per 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. Two attack patterns were identified (Request Flooding and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Sweden currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 170/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 Sweden

74.241.249.229 (340)91.92.42.120 (300)91.92.42.63 (300)51.107.182.56 (280)20.91.197.150 (280)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.

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