ABUSE.MOM
THREAT REPORT

IP Threat Report
82.162.189.245

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 08:41:18
First seen: 2026-04-06 21:36:38
Last seen: 2026-04-06 21:36:38
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
82.162.189.245
Type
Residential
Country
🇷🇺 Russia
City
Nakhodka
ISP
Primorye NET
Organization
Unknown
Autonomous System
AS12389 PJSC Rostelecom
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-06 21:36:38
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Form spam: no_js_check
2026-04-06 21:36:38
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

Primorye NET
AS12389 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 82.162.189.245 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 82.162.189.245 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
⛔ LISTED
b.barracudacentral.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net

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

10

Threat Analysis

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

📊 Threat Analysis

IP address 82.162.189.245 has been traced to Nakhodka, Russia, operating on the network of Primorye NET. 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. 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. With 190 flagged addresses, Russia represents a significant presence in our threat database. 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)72.56.191.6 (265)95.182.125.201 (265)91.240.87.225 (263)View all →

🏢 Same network: AS12389

91.122.56.59 (235)178.34.163.28 (173)87.225.37.4 (165)95.70.102.6 (165)87.225.66.136 (165)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: