IP abuse report185.254.196.109

Critical Hosting / Datacenter IPv4 Ukraine AS30860

185.254.196.109 is an IPv4 address located in Kyiv, Ukraine. It belongs to a network operated by Virtual Systems LLC (AS30860). The address is listed by 8 of the threat-intelligence sources we track and carries a confidence score of 100/100. It has also been reported 1 time(s) by the community.

Last updated Listing sources 8 Community Reports 1 How the score works
Provider notified This IP was reported to its network operator Virtual Systems LLC · 2026-11-19 · IPDB-AR-008176 Awaiting reply Show detailsHide
  1. DetectedScore 100/100
  2. Notice sent2026-11-19 23:33
  3. Deliveredv-sys.org
  4. Operator response Waiting · 4 hours ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Virtual Systems LLC's registered abuse contact on 2026-11-19 23:33: abuse@v-sys.org

This notice covers 1 address(es) on the same network. View public record · IPDB-AR-008176 →
Listing sources8
Community Reports1
Distinct Reporters1
Last seen 14 minutes ago

IP Information

ISP / Organization
Virtual Systems LLC
ASN
AS30860 YURTEH-AS
ASN Domain
v-sys.org
IP Range
185.254.196.0/22
Regional Registry
RIPENCC
Connection Type
Hosting / Datacenter
Country
Ukraine (UA)
Region / State
Kyiv City
City
Kyiv
Time Zone
Unknown
Abuse contact
abuse@v-sys.org The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Kyiv Kyiv City, Ukraine
Coordinates
50.45, 30.52
Network
AS30860 Virtual Systems LLC
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

185.254.196.0/24

2 of the 256 addresses in 185.254.196.0/24 are listed by our sources (0.8%).

Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.

Examples from the same block
185.254.196.141

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds Community reports

Blacklist Matches

8

In our pool since: 2026-11-19 01:48 (yesterday) · Last confirmed: 2026-11-20 03:50

Aggregated List (Medium Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 2 Aggregator Single address 2026-11-19 21:57 2026-11-20 03:4816 minutes ago
Attack Source 5
SourceScopeFirst seenConfirmed
Blocklist.de (all) Single address 2026-11-19 04:47 2026-11-20 03:4717 minutes ago
CZ.NIC Turris Sentinel Greylist Single address 2026-11-19 02:17 2026-11-20 03:4817 minutes ago
Data-Shield IPv4 Blocklist Single address 2026-11-19 02:48 2026-11-20 03:4915 minutes ago
Blocklist.de Brute-Force Login Single address 2026-11-19 04:48 2026-11-20 03:5014 minutes ago
IP-DB Sensor Network Single address 2026-11-19 01:48 2026-11-20 03:5014 minutes ago
Malicious Activity 1
SourceScopeFirst seenConfirmed
ThreatView High Confidence Single address 2026-11-20 02:47 2026-11-20 03:4817 minutes ago
Web Server Attack 1
SourceScopeFirst seenConfirmed
Blocklist.de Web/Apache Single address 2026-11-19 04:47 2026-11-20 03:4717 minutes ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 185.254.196.109 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 185.254.196.109 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 185.254.196.109 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 185.254.196.109 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 1

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
1Last 7 Days
1Last 30 Days
1Last 90 Days
  1. Alex Registered member
    yesterday 2026-11-19 03:59Reported from: Canada (CA)
    Reason: Port Scan
    Fail2Ban report from custom-honeypot; service=Telnet; application_protocol=Telnet; transport=TCP; destination_port=23; observed_at=2026-11-19T00:59:18Z; last_observed_at=2026-11-19T00:59:19Z; reported_at=2026-11-19T00:59:19Z matched_log_events=2; evidence_window_seconds=30; logged_tcp_connections=1; destination_ports_seen=23 2026-11-19T00:59:19Z Telnet/23 activity=client data bytes=6 credentials=<redacted> 2026-11-19T00:59:18Z Telnet/23 activity=connection accepted

Reporters' IP addresses are never published — only the country they reported from.

Listing History

1
Added to the pool
yesterday
2026-11-19 01:52

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 185.254.196.109

Is 185.254.196.109 safe?

No. 185.254.196.109 scores 100/100 with strong, recent evidence of abuse (8 sources, 1 community report). Blocking it at your firewall is advisable.

Who owns 185.254.196.109?

185.254.196.109 is announced by AS30860 and operated by Virtual Systems LLC. It sits in the 185.254.196.0/22 block registered with RIPENCC.

Where is 185.254.196.109 located?

Geolocation places 185.254.196.109 in Kyiv, Ukraine. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 185.254.196.109 on a blacklist?

Yes. 185.254.196.109 is currently listed by 8 threat sources: Blocklist.de (all), Blocklist.de Web/Apache, CZ.NIC Turris Sentinel Greylist, ThreatView High Confidence, FireHOL Level 2, Data-Shield IPv4 Blocklist….

How do I report abuse from 185.254.196.109?

Send your log lines to the network's abuse contact, abuse@v-sys.org, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/185.254.196.109

Guides for this IP