ABUSE.MOM
THREAT REPORT

IP Threat Report
37.49.224.15

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 05:20:50
First seen: 2026-06-08 04:56:15
Last seen: 2026-07-05 04:01:47
130

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
37.49.224.15
Type
Unknown
Country
🇳🇱 Netherlands
City
Amsterdam
ISP
PUSHPKT OU
Organization
PUSHPKT OU
Autonomous System
Unknown
Hit Count
1590
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 6/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 5Medium-risk: admin panels, config files+50
Directory ScanBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 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-06-08 04:56:15
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 6/2s (+35), Danger medium hits: 5 (+50)
2026-07-05 04:01:47
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 37.49.224.15 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

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

🌊 Traffic Flood Defense

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

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

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

10

Threat Analysis

37.49.224.15 has been assigned a threat score of 130/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

The address 37.49.224.15 originates from Amsterdam, Netherlands, operating on the network of PUSHPKT OU. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 1,590 malicious requests from this address across a 26-day span, reflecting a sustained attack cadence of ~61.2 requests per day. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 101 flagged addresses, Netherlands represents a significant presence in our threat database. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇳🇱 Top threats from Netherlands

91.92.43.144 (358)91.92.43.186 (358)91.92.43.190 (358)91.92.43.157 (358)91.92.43.153 (358)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.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: