ABUSE.MOM
THREAT REPORT

IP Threat Report
183.253.21.170

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:12:03
First seen: 2026-04-22 06:00:05
Last seen: 2026-04-22 06:00:05
70

⛔ Verdict: BLOCK

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

DANGER_PATHREFERER
01

Geolocation & Classification

IP Address
183.253.21.170
Type
Mobile
Country
🇨🇳 China
City
Xiamen
ISP
China Mobile
Organization
China Mobile Communications Corporation
Autonomous System
AS9808 China Mobile Communications Group Co., Ltd.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 8Medium-risk: admin panels, config files+60
Foreign referer seenReferer from unrelated external domain+10
Σ = 70
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-04-22 06:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 8 (+60), Foreign referer seen (+10)
2026-04-22 06:00:05
Last malicious request observed
Total score reached: 70/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

China Mobile
AS9808 · 🇨🇳 China
06

Recommendations

Actions taken & recommended

  • IP 183.253.21.170 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 183.253.21.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ General Security

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

07

Neighbors in 183.253.21.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

183.253.21.170 has been assigned a threat score of 70/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

📊 Threat Analysis

Threat intelligence analysis has linked 183.253.21.170 to malicious activity originating from Xiamen, China, operating on the network of China Mobile. The address has been under observation since its initial detection. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Our records show 167 malicious IPs originating from China, positioning it as a significant contributor to global threat activity. At 70/100, this IP warrants immediate defensive action.

11

Related Threats

🇨🇳 Top threats from China

180.184.55.222 (340)117.50.120.215 (235)115.191.1.205 (235)123.58.16.244 (235)43.142.47.248 (230)View all →

🏢 Same network: AS9808

183.207.48.161 (230)36.212.132.184 (220)117.156.171.166 (200)112.51.229.143 (180)36.138.252.97 (170)View all →
12

Security Intelligence

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

💡 Container Security Challenges

Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.

🔍 Check Any IP Address

Share this report: