ABUSE.MOM
THREAT REPORT

IP Threat Report
103.1.224.174

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-05 04:11:05
First seen: 2026-06-13 08:36:21
Last seen: 2026-07-05 04:02:42
145

⛔ Verdict: BLOCK

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

BOT_UABURSTREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
103.1.224.174
Type
Unknown
Country
🇯🇵 Japan
City
Ueda
ISP
N963
Organization
N963
Autonomous System
Unknown
Hit Count
1383
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 56/2sAbnormally fast request rate — automated scanning+35
Burst 61/10sAbnormally fast request rate — automated scanning+35
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 145
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-06-13 08:36:21
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 56/2s (+35), Burst 61/10s (+35), DDoS / Flood
2026-07-05 04:02:42
Last malicious request observed
Total score reached: 145/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 103.1.224.174 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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 103.1.224.174.

🤖 Bot Detection

Address UA spoofing from 103.1.224.174: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
bl.spamcop.net
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

103.1.224.174 has been assigned a threat score of 145/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Network traffic from 103.1.224.174, located in Ueda, Japan, operating on the network of N963, has been classified as malicious by our automated threat scoring engine. The address has been active for 21 days in our monitoring system, producing 1,383 flagged requests at a rate of ~65.9/day. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. Our records show 101 malicious IPs originating from Japan, positioning it as a significant contributor to global threat activity. With a threat score of 145/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

11

Related Threats

🇯🇵 Top threats from Japan

103.163.220.216 (340)35.189.151.182 (320)34.97.45.15 (295)35.243.110.60 (288)20.194.153.120 (280)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 CAPTCHA and Bot Detection

CAPTCHAs remain a primary bot defense but face increasing bypass rates from AI-powered solvers. Modern alternatives include invisible behavioral analysis, proof-of-work challenges, and device fingerprinting that detect bots without impacting user experience.

🔍 Check Any IP Address

Share this report: