
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: axios | Known bot/crawler User-Agent detected | +40 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +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 212.41.13.28: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Block scanning from 212.41.13.28: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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.
212.41.13.28 has been assigned a threat score of 65/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.
The following attack categories were identified:
Our monitoring infrastructure has identified 212.41.13.28, geolocated to St Petersburg, Russia, operating on the network of JSC Selectel, as a source of suspicious network activity. The address has been active for 5 days in our monitoring system, producing 2 flagged requests at a rate of ~0.4/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 dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 140 flagged addresses, Russia represents a significant presence in our threat database. The score of 65/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.
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.
Proper network segmentation limits the blast radius of breaches. Even if attackers compromise one segment, properly configured network boundaries prevent lateral movement to critical systems, databases, and administrative interfaces.