
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 8 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 12 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 13.61.5.57 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 13.61.5.57 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 626 | Unknown | Low | Service on port 626 |
| 2806 | Unknown | Low | Service on port 2806 |
| 3059 | Unknown | Low | Service on port 3059 |
| 9074 | Unknown | Low | Service on port 9074 |
| 9353 | Unknown | Low | Service on port 9353 |
| 9418 | Unknown | Low | Service on port 9418 |
| 18038 | Unknown | Low | Service on port 18038 |
| CVE ID | Link |
|---|---|
| CVE-2021-40438 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2020-11579 | NVD → |
| CVE-2020-13938 | NVD → |
| CVE-2018-10548 | NVD → |
| CVE-2020-9490 | NVD → |
| CVE-2018-19935 | NVD → |
| CVE-2019-10092 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2020-35452 | NVD → |
| CVE-2018-1301 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2017-3169 | NVD → |
| CVE-2020-7062 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2020-7066 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2024-43394 | NVD → |
| CVE-2024-38477 | NVD → |
| CVE-2024-43204 | NVD → |
| CVE-2019-0211 | NVD → |
| CVE-2018-1303 | NVD → |
| CVE-2020-7069 | NVD → |
| CVE-2020-7061 | NVD → |
| CVE-2018-14851 | NVD → |
🔴 Security scanning identified 156 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
13.61.5.57 has been assigned a threat score of 170/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:
Threat intelligence analysis has linked 13.61.5.57 to malicious activity originating from Stockholm, Sweden, operating on the network of Amazon.com, Inc.. The address has been under observation since its initial detection. Over a period of 1 days, this IP generated 2 malicious requests, averaging approximately 2 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Sweden currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. A score of 170/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.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.
DNS amplification exploits open resolvers to reflect and amplify traffic toward victims. A small query triggers a large response directed at the spoofed source IP, achieving amplification factors of 50x or more, overwhelming target bandwidth.