ABUSE.MOM
THREAT REPORT

IP Threat Report
185.253.102.29

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 05:17:49
First seen: 2026-04-25 04:58:54
Last seen: 2026-04-25 04:58:54
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.

FORM_SPAM
01

Geolocation & Classification

IP Address
185.253.102.29
Type
Residential
Country
🇷🇺 Russia
City
Pyatigorsk
ISP
OOO "Post ltd"
Organization
OOO "Post ltd"
Autonomous System
AS12494 OOO Post ltd
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Form spam: no_js_checkSpam/malware keywords in request content+0
Σ = 0
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-25 04:58:54
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Form spam: no_js_check
2026-04-25 04:58:54
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

OOO "Post ltd"
AS12494 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

📧 Content Abuse Prevention

IP 185.253.102.29 is flooding forms with spam. Implement time-based tokens and block IPs submitting more than 5 forms per hour.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

185.253.102.29 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

IP address 185.253.102.29 has been traced to Pyatigorsk, Russia, operating on the network of OOO "Post ltd". Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Russia currently accounts for 102 blocked IPs in our database, making it a significant source of malicious traffic. A threat score of 70/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

157.22.102.172 (313)178.130.54.159 (288)95.182.125.201 (265)72.56.191.6 (265)91.240.87.225 (263)View all →

🏢 Same network: AS12494

5.133.76.121 (60)View all →
12

Security Intelligence

💡 SQL Injection Campaigns

SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.

💡 GeoIP Blocking Considerations

Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.

🔍 Check Any IP Address

Share this report: