ABUSE.MOM
THREAT REPORT

IP Threat Report
104.207.58.151

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 02:42:59
First seen: 2026-09-11 12:56:02
Last seen: 2026-09-13 01:16:55
110

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
104.207.58.151
Type
Unknown
Country
🇤🇤 ??
City
Unknown
ISP
Unknown
Organization
Unknown
Autonomous System
Unknown
Hit Count
51
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Foreign refererReferer from unrelated external domain+10
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 110
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-09-11 12:56:02
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: 1 (+10), Danger strong hits: 2 (+50)
2026-09-13 01:16:55
Last malicious request observed
Total score reached: 110/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 104.207.58.151 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🤖 Bot Detection

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

07

Neighbors in 104.207.58.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
zen.spamhaus.org
✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

104.207.58.151 has been assigned a threat score of 110/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 EnumerationUser-Agent Anomaly

📊 Threat Analysis

104.207.58.151 is registered in an unknown location. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 1-day observation window, we recorded 51 hostile requests from this IP — roughly 51 per day on average. The dual attack vectors of Path Enumeration combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. A score of 110/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇤🇤 Top threats from ??

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.

💡 Memory Safety and Buffer Overflows

Buffer overflow vulnerabilities remain relevant in C/C++ applications despite decades of mitigation efforts. Modern protections like ASLR, stack canaries, and DEP reduce exploitability but determined attackers continue finding bypass techniques.

🔍 Check Any IP Address

Share this report: