
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.
Add 120.231.175.150 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.
120.231.175.150 has been assigned a threat score of 115/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
120.231.175.150 is registered in Zhuhai, China, operating on the network of China Mobile communications corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 1,140 malicious requests from this address across a 21-day span, reflecting a sustained attack cadence of ~54.3 requests per day. Our records show 103 malicious IPs originating from China, positioning it as a significant contributor to global threat activity. With a threat score of 115/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.