
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 15 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 11 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 17 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 9 req / 2s | 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.
Block scanning from 159.223.38.87: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 159.223.38.87.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| CVE ID | Link |
|---|---|
| CVE-2025-53020 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2024-47252 | NVD → |
| CVE-2025-23048 | NVD → |
| CVE-2024-38474 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2024-43204 | NVD → |
| CVE-2009-2299 | NVD → |
| CVE-2024-43394 | NVD → |
| CVE-2012-4001 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2024-38476 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2023-38709 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2012-4360 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2024-27316 | NVD → |
| CVE-2013-4365 | NVD → |
🔴 Security scanning identified 37 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.
159.223.38.87 has been assigned a threat score of 180/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:
Threat intelligence analysis has linked 159.223.38.87 to malicious activity originating from Singapore, Singapore, operating on the network of DigitalOcean, LLC. The address has been under observation since its initial detection. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/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 (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Singapore currently accounts for 140 blocked IPs in our database, making it a significant source of malicious traffic. A score of 180/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.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
WAFs inspect HTTP traffic to block common attacks but require careful tuning. Overly aggressive rules cause false positives while permissive configurations miss attacks. Modern WAFs combine signature matching with behavioral analysis and machine learning.