ABUSE.MOM
THREAT REPORT

IP Threat Report
192.171.87.62

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:56:21
First seen: 2026-02-17 17:25:05
Last seen: 2026-03-24 23:00:06
200

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 200/100. Total malicious requests observed: 39.

UA_CHANGEDDANGER_PATHRATIO_404REDIRECT_PROBEBURSTREFERERIMPORT
01

Geolocation & Classification

IP Address
192.171.87.62
Type
Residential
Country
🇺🇸 United States
City
San Francisco
ISP
Sprious LLC
Organization
Blazing SEO, LLC
Autonomous System
AS64267 Sprious LLC
Hit Count
39
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger medium hits: 46Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Danger medium hits: 24Medium-risk: admin panels, config files+60
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger medium hits: 8Medium-risk: admin panels, config files+60
Danger medium hits: 14Medium-risk: admin panels, config files+60
Burst: 8 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 12Medium-risk: admin panels, config files+60
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 550
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-02-17 17:25:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger medium hits: 46 (+60), 404 ratio 40-60% (+15)
2026-03-24 23:00:06
Last malicious request observed
Total score reached: 200/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Sprious LLC
AS64267 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 192.171.87.62 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

Address UA spoofing from 192.171.87.62: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Path Enumeration Protection

Block scanning from 192.171.87.62: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 192.171.87.62.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
4444UnknownLowService on port 4444
8000UnknownLowService on port 8000
KNOWN VULNERABILITIES (CVE) (27)
CVE IDLink
CVE-2023-46724NVD →
CVE-2023-49286NVD →
CVE-2025-59362NVD →
CVE-2021-33620NVD →
CVE-2024-45802NVD →
CVE-2023-5824NVD →
CVE-2024-25617NVD →
CVE-2023-49288NVD →
CVE-2021-46784NVD →
CVE-2025-62168NVD →
CVE-2021-28116NVD →
CVE-2023-46728NVD →
CVE-2021-28651NVD →
CVE-2022-41318NVD →
CVE-2023-50269NVD →
CVE-2021-28652NVD →
CVE-2024-37894NVD →
CVE-2021-31807NVD →
CVE-2025-54574NVD →
CVE-2024-25111NVD →
CVE-2023-46847NVD →
CVE-2021-31808NVD →
CVE-2023-46846NVD →
CVE-2021-28662NVD →
CVE-2022-41317NVD →
+2 more

🔴 This host has 27 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.

DETECTED TECHNOLOGIES
squid-cache:squid:4.14
Hostnames: host-192-171-87-62.static.sprious.com
PTR: host-192-171-87-62.static.sprious.com

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
Spamhaus ZEN

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

192.171.87.62 has been assigned a threat score of 200/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:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

192.171.87.62 is registered in San Francisco, United States, operating on the network of Sprious LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 39 malicious requests from this address across a 35-day span, reflecting a sustained attack cadence of ~1.1 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 202 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 200/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS64267

66.146.236.62 (200)216.213.28.68 (200)162.244.145.212 (180)199.34.84.33 (180)139.180.224.102 (180)View all →
12

Security Intelligence

💡 HTTP Header Analysis for Threat Detection

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.

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

🔍 Check Any IP Address

Share this report: