ABUSE.MOM
THREAT REPORT

IP Threat Report
151.240.45.102

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-12 01:16:51
First seen: 2026-05-31 00:45:47
Last seen: 2026-07-12 00:42:28
90

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
151.240.45.102
Type
Unknown
Country
🇺🇸 United States
City
Boston
ISP
Datacamp Limited
Organization
Datacamp Limited
Autonomous System
Unknown
Hit Count
22
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Directory ScanBehavioral anomaly detected by automated analysis+0
Σ = 60
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-05-31 00:45:47
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger medium hits: 1 (+10), Danger strong hits: 1 (+25)
2026-07-12 00:42:28
Last malicious request observed
Total score reached: 90/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

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

07

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

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

10

Threat Analysis

151.240.45.102 has been assigned a threat score of 90/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 151.240.45.102, geolocated to Boston, United States, operating on the network of Datacamp Limited, as a source of suspicious network activity. Over a period of 41 days, this IP generated 22 malicious requests, averaging approximately 0.5 requests per day. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 147 flagged addresses, United States represents a significant presence in our threat database. A score of 90/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

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

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

🔍 Check Any IP Address

Share this report: