
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Directory Scan | Behavioral anomaly detected by automated analysis | +0 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block 114.119.128.127 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
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.
114.119.128.127 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
Network traffic from 114.119.128.127, located in Singapore, Singapore, operating on the network of Huawei International Pte. Ltd., has been classified as malicious by our automated threat scoring engine. Our sensors captured 813 malicious requests from this address across a 36-day span, reflecting a sustained attack cadence of ~22.6 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Singapore currently accounts for 104 blocked IPs in our database, making it a significant source of malicious traffic. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.
Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.