ABUSE.MOM
THREAT REPORT

IP Threat Report
135.136.40.30

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 18:49:41
First seen: 2026-06-10 10:43:41
Last seen: 2026-06-27 23:57:20
255

⛔ Verdict: BLOCK

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

01

Geolocation & Classification

IP Address
135.136.40.30
Type
Unknown
Country
🇳🇬 NG
City
Lagos
ISP
M247 Global
Organization
M247 Global
Autonomous System
Unknown
Hit Count
72
02

Detection Signatures

SignatureDescriptionPointsSeverity
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Σ = 0
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-10 10:43:41
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
DDoS / Flood
2026-06-27 23:57:20
Last malicious request observed
Total score reached: 255/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

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

⚙️ General Security

Add 135.136.40.30 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

07

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

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

10

Threat Analysis

135.136.40.30 has been assigned a threat score of 255/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

📊 Threat Analysis

Network traffic from 135.136.40.30, located in Lagos, NG, operating on the network of M247 Global, has been classified as malicious by our automated threat scoring engine. Our sensors captured 72 malicious requests from this address across a 17-day span, reflecting a sustained attack cadence of ~4.2 requests per day. NG currently accounts for 61 blocked IPs in our database, making it a notable source of malicious traffic. A score of 255/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇳🇬 Top threats from NG

135.136.40.234 (255)135.136.40.239 (255)135.136.40.135 (255)105.127.17.59 (208)143.105.103.35 (163)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Network Flow Analysis

Analyzing network flows (NetFlow, sFlow, IPFIX) provides visibility into traffic patterns without inspecting packet contents. Flow data reveals scanning activity, data exfiltration, lateral movement, and command-and-control channels at scale.

🔍 Check Any IP Address

Share this report: