ABUSE.MOM
THREAT REPORT

IP Threat Report
162.241.252.224

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 18:03:16
First seen: 2026-08-15 04:53:09
Last seen: 2026-08-23 02:04:04
70

⛔ Verdict: BLOCK

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

DANGER_PATH
01

Geolocation & Classification

IP Address
162.241.252.224
Type
Hosting
Country
🇺🇸 United States
City
Phoenix
ISP
Oracle Corporation
Organization
Unified Layer
Autonomous System
AS31898 Oracle Corporation
Hit Count
199
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Σ = 70
03

Observed Activity

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

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

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

04

Timeline

2026-08-15 04:53:09
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 2 (+20), Danger strong hits: 2 (+50)
2026-08-23 02:04:04
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Oracle Corporation
AS31898 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 162.241.252.224 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

09

Blacklist Status (DNSBL)

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

✓ Clean
bl.blocklist.de
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

162.241.252.224 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.

📊 Threat Analysis

162.241.252.224 is registered in Phoenix, United States, operating on the network of Oracle Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 7 days in our monitoring system, producing 199 flagged requests at a rate of ~28.4/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. Our records show 21 malicious IPs originating from United States, positioning it as a notable contributor to global threat activity. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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.

11

Related Threats

🇺🇸 Top threats from United States

129.225.5.36 (310)147.224.242.137 (263)162.144.3.250 (255)50.6.108.183 (255)129.213.151.234 (240)View all →

🏢 Same network: AS31898

168.110.63.243 (320)129.151.133.112 (320)81.208.175.87 (320)129.225.5.36 (310)140.245.63.215 (310)View all →
12

Security Intelligence

💡 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.

💡 IPv6 Scanning Challenges

The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.

🔍 Check Any IP Address

Share this report: