IP Threat Report
203.198.28.191
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA bot: python | Known bot/crawler User-Agent detected | +40 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Recommendations
Actions taken & recommended
- IP 203.198.28.191 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Path Enumeration Protection
Block scanning from 203.198.28.191: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🤖 User-Agent Anomaly Defense
IP 203.198.28.191 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
203.198.28.191 has been assigned a threat score of 175/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
IP address 203.198.28.191 has been traced to Central, Hong Kong, operating on the network of PCCW IMS Limited. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 1,093 malicious requests from this address across a 37-day span, reflecting a sustained attack cadence of ~29.5 requests per day. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Hong Kong currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 175/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
Related Threats
🇭🇰 Top threats from Hong Kong
20.24.198.93 (280)20.24.82.132 (280)20.187.125.76 (280)20.187.67.15 (280)20.205.115.105 (280)View all →Security Intelligence
💡 Cross-Site Scripting (XSS) Attacks
XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.
💡 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.