ABUSE.MOM
THREAT REPORT

IP Threat Report
38.60.221.123

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 13:34:15
First seen: 2026-05-25 10:42:30
Last seen: 2026-05-27 13:27:35
73

⛔ Verdict: BLOCK

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

BOT_UAMETHODUA_CHANGED
01

Geolocation & Classification

IP Address
38.60.221.123
Type
Residential
Country
🇷🇺 Russia
City
Moscow
ISP
Kaopu Cloud HK Limited
Organization
LightNode-RU
Autonomous System
AS138915 Kaopu Cloud HK Limited
Hit Count
459
02

Detection Signatures

SignatureDescriptionPointsSeverity
POST seenBehavioral anomaly detected by automated analysis+8
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 73
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-05-25 10:42:30
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
POST seen (+8), UA bot: python (+40), UA changed (+25)
2026-05-27 13:27:35
Last malicious request observed
Total score reached: 73/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Kaopu Cloud HK Limited
AS138915 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 38.60.221.123 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

Address UA spoofing from 38.60.221.123: 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
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

38.60.221.123 has been assigned a threat score of 73/100 (High). This classifies it as a high-severity threat. Proactive blocking is recommended for sensitive infrastructure.

The following attack categories were identified:

User-Agent Anomaly

📊 Threat Analysis

IP address 38.60.221.123 has been traced to Moscow, Russia, operating on the network of Kaopu Cloud HK Limited. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 459 malicious requests from this address across a 2-day span, reflecting a sustained attack cadence of ~229.5 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. A threat score of 73/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇷🇺 Top threats from Russia

View all →

🏢 Same network: AS138915

38.54.29.82 (168)154.205.148.248 (130)38.60.255.59 (130)156.244.2.102 (105)156.244.33.216 (105)View all →
12

Security Intelligence

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 Web Cache Poisoning Attacks

Cache poisoning manipulates web cache behavior to serve malicious content to other users. By identifying unkeyed inputs that influence cached responses, attackers can inject JavaScript, redirect users, or cause denial of service at scale through the cache infrastructure.

🔍 Check Any IP Address

Share this report: