ABUSE.MOM
THREAT REPORT

IP Threat Report
202.187.158.69

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 09:02:29
First seen: 2026-03-13 07:00:06
Last seen: 2026-03-13 07:00:06
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
202.187.158.69
Type
Residential
Country
🇲🇾 MY
City
Kuala Lumpur
ISP
TT DOTCOM SDN BHD
Organization
TT DOTCOM SDN BHD
Autonomous System
AS9930 TTNET-MY
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
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-03-13 07:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-03-13 07:00:06
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

TT DOTCOM SDN BHD
AS9930 · 🇲🇾 MY
06

Recommendations

Actions taken & recommended

  • IP 202.187.158.69 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 202.187.158.69 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.

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

202.187.158.69 has been assigned a threat score of 103/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

📊 Threat Analysis

202.187.158.69 is registered in Kuala Lumpur, MY, operating on the network of TT DOTCOM SDN BHD. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. With 101 flagged addresses, MY represents a significant presence in our threat database. With a threat score of 103/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇲🇾 Top threats from MY

173.239.236.80 (305)101.99.94.104 (265)173.239.236.211 (255)173.239.236.71 (255)173.239.236.44 (255)View all →

🏢 Same network: AS9930

202.184.66.66 (208)161.142.148.210 (180)161.142.148.13 (130)161.142.156.212 (93)161.142.117.212 (93)View all →
12

Security Intelligence

💡 SQL Injection Campaigns

SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.

💡 Rate Limiting and Throttling Strategies

Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.

🔍 Check Any IP Address

Share this report: