
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
We have detected 7023 malicious IPs from this autonomous system.
Address UA spoofing from 142.93.75.106: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.
142.93.75.106 has been assigned a threat score of 85/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:
Network traffic from 142.93.75.106, located in Clifton, United States, operating on the network of DigitalOcean, LLC, has been classified as malicious by our automated threat scoring engine. During its 2-day observation window, we recorded 74 hostile requests from this IP — roughly 37 per day on average. 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 IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. United States currently accounts for 36,314 blocked IPs in our database, making it a major source of malicious traffic. A threat score of 85/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.
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.
XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.
CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.