
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 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: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 14 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 7 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.
IP 35.236.78.213 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Block scanning from 35.236.78.213: 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 35.236.78.213.
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 5000 | Unknown | Low | Service on port 5000 |
| CVE ID | Link |
|---|---|
| CVE-2025-12781 | NVD → |
| CVE-2024-9287 | NVD → |
| CVE-2025-13836 | NVD → |
| CVE-2023-40217 | NVD → |
| CVE-2020-29396 | NVD → |
| CVE-2009-3720 | NVD → |
| CVE-2021-32052 | NVD → |
| CVE-2025-12084 | NVD → |
| CVE-2023-27043 | NVD → |
| CVE-2023-36632 | NVD → |
| CVE-2009-2940 | NVD → |
| CVE-2024-6232 | NVD → |
| CVE-2025-13837 | NVD → |
| CVE-2024-7592 | NVD → |
🔴 Security scanning identified 14 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.
35.236.78.213 has been assigned a threat score of 180/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
IP address 35.236.78.213 has been traced to Los Angeles, United States, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 2 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~2 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. United States currently accounts for 142 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.
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
Nation-state actors conduct sophisticated campaigns for espionage, sabotage, and influence operations. Their resources exceed typical criminal organizations, enabling zero-day exploitation, long-term persistent access, and attacks on critical infrastructure.