ABUSE.MOM
THREAT REPORT

IP Threat Report
71.162.163.122

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:47:17
First seen: 2026-04-10 19:00:06
Last seen: 2026-04-10 19:00:06
210

⛔ Verdict: BLOCK

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

DANGER_PATHBURSTREFERER
01

Geolocation & Classification

IP Address
71.162.163.122
Type
Residential
Country
🇺🇸 United States
City
Philadelphia
ISP
Verizon Business
Organization
Verizon Business
Autonomous System
AS701 Verizon Business
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 3Medium-risk: admin panels, config files+30
Burst: 26 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 34 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 210
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-04-10 19:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 6 (+100), Danger medium hits: 3 (+30), Burst: 26 req / 2s (+35)
2026-04-10 19:00:06
Last malicious request observed
Total score reached: 210/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Verizon Business
AS701 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 71.162.163.122 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

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

⛔ LISTED
b.barracudacentral.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

71.162.163.122 has been assigned a threat score of 210/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 71.162.163.122, geolocated to Philadelphia, United States, operating on the network of Verizon Business, as a source of suspicious network activity. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. United States currently accounts for 128 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 210/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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: AS701

100.36.123.148 (180)100.40.126.12 (180)96.231.211.94 (135)96.253.85.198 (135)100.36.150.7 (130)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

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.

💡 Threat Score Calculation Methods

Threat scoring combines multiple signals — request patterns, known signatures, IP reputation, geographic risk, and behavioral analysis — into a single actionable metric. Weighted scoring models allow tuning sensitivity to balance security with usability.

🔍 Check Any IP Address

Share this report: