
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 9 | Medium-risk: admin panels, config files | +60 | |
| Burst: 5 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 11 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Referer points to .php on your site | Referer from unrelated external domain | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 187.91.168.111.
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 |
| 123 | Unknown | Low | Service on port 123 |
| 161 | Unknown | Low | Service on port 161 |
| CVE ID | Link |
|---|---|
| CVE-2023-48795 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2016-10011 | NVD → |
| CVE-2015-5600 | NVD → |
| CVE-2016-0777 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2016-3115 | NVD → |
| CVE-2016-10009 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2016-10012 | NVD → |
| CVE-2016-0778 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2019-6111 | NVD → |
| CVE-2015-5352 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2015-6563 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2017-15906 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2018-15919 | NVD → |
🔴 Security scanning identified 31 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.
187.91.168.111 has been assigned a threat score of 245/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
Threat intelligence analysis has linked 187.91.168.111 to malicious activity originating from Fortaleza, Brazil, operating on the network of Vivo. The address has been under observation since its initial detection. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. With 101 flagged addresses, Brazil represents a significant presence in our threat database. With a threat score of 245/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.
Email authentication protocols work together to prevent spoofing. SPF validates sending servers, DKIM provides cryptographic message signing, and DMARC defines enforcement policies. Full implementation significantly reduces phishing effectiveness.