
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA bot: python | Known bot/crawler User-Agent detected | +40 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Address UA spoofing from 130.210.56.65: 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.
130.210.56.65 has been assigned a threat score of 73/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
The address 130.210.56.65 originates from Mumbai, India, operating on the network of Oracle Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 4 days, this IP generated 374 malicious requests, averaging approximately 93.5 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. With 4,292 flagged addresses, India represents a major presence in our threat database. At 73/100, this IP warrants immediate defensive action.
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.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
Internet traffic routing through a limited number of submarine cables and exchange points creates natural chokepoints. Understanding these routing patterns helps explain geographic clustering of certain attack types and latency-based scanning behaviors.