ABUSE.MOM
THREAT REPORT

IP Threat Report
154.212.31.180

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 12:47:33
First seen: 2026-03-12 20:00:07
Last seen: 2026-03-16 16:00:05
110

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHREDIRECT_PROBE
01

Geolocation & Classification

IP Address
154.212.31.180
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
IT HOST BKPL
Organization
Unknown
Autonomous System
AS49505 JSC Selectel
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: axiosKnown bot/crawler User-Agent detected+40
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 110
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-03-12 20:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: axios (+40), Danger strong hits: 2 (+50), Probe pattern 302->404 same path (+20)
2026-03-16 16:00:05
Last malicious request observed
Total score reached: 110/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

IT HOST BKPL
AS49505 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 154.212.31.180 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 154.212.31.180: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

🔎 Directory Scan Defense

IP 154.212.31.180 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (2)
PortServiceRiskDescription
123UnknownLowService on port 123
24442UnknownLowService on port 24442
DETECTED TECHNOLOGIES
debian:debian_linuxlinux:linux_kernelntp:ntp:3openbsd:openssh:9.2p1

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

154.212.31.180 has been assigned a threat score of 110/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

154.212.31.180 is registered in Moscow, Russia, operating on the network of IT HOST BKPL. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 3 days, this IP generated 3 malicious requests, averaging approximately 1 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (User-Agent Anomaly and Path Enumeration), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 140 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. A score of 110/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

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

212.41.9.153 (245)194.156.93.146 (140)45.132.38.125 (140)85.142.132.11 (140)85.142.3.163 (140)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Content Delivery Network Risks

CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.

🔍 Check Any IP Address

Share this report: