ABUSE.MOM
THREAT REPORT

IP Threat Report
107.150.3.202

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 01:20:00
First seen: 2026-06-13 01:30:54
Last seen: 2026-07-05 04:01:53
130

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
107.150.3.202
Type
Unknown
Country
🇺🇸 United States
City
Chicago
ISP
HostPapa
Organization
HostPapa
Autonomous System
Unknown
Hit Count
645
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 5Medium-risk: admin panels, config files+50
Directory ScanBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 95
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-06-13 01:30:54
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 5 (+50), Directory Scan
2026-07-05 04:01:53
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 107.150.3.202 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 107.150.3.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

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

07

Neighbors in 107.150.3.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

Network traffic from 107.150.3.202, located in Chicago, United States, operating on the network of HostPapa, has been classified as malicious by our automated threat scoring engine. Our sensors captured 645 malicious requests from this address across a 22-day span, reflecting a sustained attack cadence of ~29.3 requests per day. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 104 blocked IPs in our database, making it a significant source of malicious traffic. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.215.74.213 (340)103.168.66.237 (340)34.187.158.4 (340)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 Mobile Malware Distribution

Mobile malware reaches devices through unofficial app stores, malicious links, and even occasionally through official stores using obfuscation techniques. Banking trojans, spyware, and ransomware variants specifically designed for mobile platforms continue to proliferate.

🔍 Check Any IP Address

Share this report: