ABUSE.MOM
THREAT REPORT

IP Threat Report
46.20.74.185

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 11:33:35
First seen: 2026-02-17 17:25:07
Last seen: 2026-02-17 17:26:16
80

⛔ Verdict: BLOCK

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

BURSTREFERERIMPORT
01

Geolocation & Classification

IP Address
46.20.74.185
Type
Residential
Country
🇷🇺 Russia
City
Samara
ISP
SAMARA-TTK
Organization
CJSC "Samara-Transtelecom"
Autonomous System
AS15774 Limited Liability Company "TTK-Svyaz"
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 19 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 19 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Σ = 80
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-02-17 17:25:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 19 req / 2s (+35), Burst: 19 req / 10s (+35), Foreign referer seen (+10)
2026-02-17 17:26:16
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

SAMARA-TTK
AS15774 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

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

09

Blacklist Status (DNSBL)

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

✓ Clean
Spamhaus ZEN

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

10

Threat Analysis

46.20.74.185 has been assigned a threat score of 80/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 Flooding

📊 Threat Analysis

Network traffic from 46.20.74.185, located in Samara, Russia, operating on the network of SAMARA-TTK, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 3 malicious requests, averaging approximately 3 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 102 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. At 80/100, this IP warrants immediate defensive action.

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: AS15774

176.125.98.4 (80)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.

💡 Zero Trust Architecture Principles

Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.

🔍 Check Any IP Address

Share this report: