IP Threat Report
45.84.107.17
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Form spam: latin_name | Spam/malware keywords in request content | +0 | |
| Form spam: too_fast | Spam/malware keywords in request content | +0 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA bot: Go-http-client | Known bot/crawler User-Agent detected | +40 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 45.84.107.17 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 45.84.107.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 45.84.107.17 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
📧 Content Abuse Prevention
IP 45.84.107.17 is flooding forms with spam. Implement time-based tokens and block IPs submitting more than 5 forms per hour.
🤖 Bot Detection
Address UA spoofing from 45.84.107.17: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Neighbors in 45.84.107.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
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.
Threat Analysis
45.84.107.17 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:
📊 Threat Analysis
Our monitoring infrastructure has identified 45.84.107.17, geolocated to Sundbyberg, Sweden, operating on the network of QuxLabs AB, as a source of suspicious network activity. Over a period of 96 days, this IP generated 46 malicious requests, averaging approximately 0.5 requests per day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 110 malicious IPs originating from Sweden, positioning it as a significant contributor to global threat activity. The score of 73/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.
Related Threats
🇸🇪 Top threats from Sweden
74.241.249.229 (340)91.92.42.63 (300)91.92.42.120 (300)51.107.182.56 (280)20.91.197.150 (280)View all →Security Intelligence
💡 SQL Injection Campaigns
SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.
💡 HTTP/2 and HTTP/3 Security Implications
Modern HTTP protocols introduce new attack surfaces including stream multiplexing abuse, header compression attacks (HPACK bombing), and rapid reset attacks. Security tools must evolve to handle these protocol-specific threats effectively.