
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: python | Known bot/crawler User-Agent detected | +40 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Imported from old blocklist | Behavioral anomaly detected by automated analysis | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 107.189.25.71 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 21 | FTP | Medium | File Transfer Protocol — often targeted for anonymous login attacks |
| 53 | DNS | Low | DNS server — potential for DNS amplification attacks |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 587 | Unknown | Low | Service on port 587 |
| 993 | IMAPS | Low | Service on port 993 |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
⚠️ Network scanning reveals 2 dangerous services exposed on 107.189.25.71. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2023-42114 | NVD → |
| CVE-2023-42115 | NVD → |
| CVE-2022-3559 | NVD → |
| CVE-2023-42116 | NVD → |
| CVE-2023-51766 | NVD → |
| CVE-2022-37451 | NVD → |
| CVE-2022-3620 | NVD → |
| CVE-2023-42117 | NVD → |
| CVE-2024-39929 | NVD → |
| CVE-2023-42119 | NVD → |
| CVE-2025-67896 | NVD → |
🔴 Security scanning identified 11 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.
107.189.25.71 has been assigned a threat score of 50/100 (Medium). The address carries a moderate risk rating. Defensive monitoring is advised, with escalation to blocking if activity intensifies.
The following attack categories were identified:
IP address 107.189.25.71 has been traced to Zaandam, Netherlands, operating on the network of RouterHosting LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 3 flagged requests at a rate of ~3/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. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. Our records show 107 malicious IPs originating from Netherlands, positioning it as a significant contributor to global threat activity. At 50/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.