<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Firewall Security &#8211; pk-360</title>
	<atom:link href="https://pk-360.com/tag/firewall-security/feed/" rel="self" type="application/rss+xml" />
	<link>https://pk-360.com</link>
	<description>IT Solutions, Support, Insight, Ideas, and Business Solutions</description>
	<lastBuildDate>Thu, 17 Sep 2026 10:09:40 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://pk-360.com/wp-content/uploads/2025/08/pk-360-150x150.png</url>
	<title>Firewall Security &#8211; pk-360</title>
	<link>https://pk-360.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>MikroTik Router Security: Protect Against Brute-Force Attacks</title>
		<link>https://pk-360.com/mikrotik-router-security-alert/</link>
					<comments>https://pk-360.com/mikrotik-router-security-alert/#respond</comments>
		
		<dc:creator><![CDATA[Haider]]></dc:creator>
		<pubDate>Tue, 15 Sep 2026 06:32:21 +0000</pubDate>
				<category><![CDATA[Cyber Security]]></category>
		<category><![CDATA[Cyber Advisory]]></category>
		<category><![CDATA[Brute Force Attack]]></category>
		<category><![CDATA[cybersecurity]]></category>
		<category><![CDATA[Firewall Security]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[MikroTik]]></category>
		<category><![CDATA[MikroTik RouterOS]]></category>
		<category><![CDATA[MikroTik Security]]></category>
		<category><![CDATA[network protection]]></category>
		<category><![CDATA[network security]]></category>
		<category><![CDATA[Router Security]]></category>
		<category><![CDATA[Router Security Alert]]></category>
		<guid isPermaLink="false">https://pk-360.com/?p=2166</guid>

					<description><![CDATA[Published: September 2026Category: Cybersecurity / Network SecuritySeverity: 🔴 High MikroTik Router Security: Protect Against Brute-Force Attacks. Organizations using MikroTik routers should take immediate steps to review and secure their internet-facing devices. A heightened cybersecurity risk has been identified involving automated scanning, brute-force attacks, exploitation attempts, and unauthorized access targeting publicly reachable MikroTik routers. The risk]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><strong>Published:</strong> September 2026<br><strong>Category:</strong> <a href="https://pk-360.com/closure-migration-of-insecure-email-services-at-ntc/">Cybersecurity </a>/ Network Security<br><strong>Severity:</strong> 🔴 High</p>



<p class="wp-block-paragraph">MikroTik Router Security: Protect Against Brute-Force Attacks. Organizations using <strong>MikroTik routers</strong> should take immediate steps to review and secure their internet-facing devices. A heightened cybersecurity risk has been identified involving automated scanning, brute-force attacks, exploitation attempts, and unauthorized access targeting publicly reachable MikroTik routers.</p>



<p class="wp-block-paragraph">The risk is particularly important for organizations operating routers in government, enterprise, educational, financial, healthcare, and other sensitive environments.</p>



<p class="wp-block-paragraph">Attackers are actively looking for MikroTik devices whose management interfaces are exposed to the public internet. Devices running outdated RouterOS versions, using weak passwords, retaining default configurations, or exposing unnecessary management services can be especially vulnerable.</p>



<h2 class="wp-block-heading">What Is the <a href="https://pk-360.com/new-cybersecurity-warning-ransomware-actors-tied-to-lockbit/">Threat?</a></h2>



<p class="wp-block-paragraph">Cybercriminals can scan publicly accessible IP addresses to identify MikroTik routers and determine whether services such as <strong>Winbox, WebFig, SSH, SNMP, or REST API</strong> are accessible.</p>



<p class="wp-block-paragraph">Once a vulnerable or poorly configured router is identified, attackers may attempt to:</p>



<ul class="wp-block-list">
<li>Guess administrative passwords through automated brute-force attacks</li>



<li>Identify valid administrative usernames</li>



<li>Exploit vulnerabilities in outdated RouterOS versions</li>



<li>Obtain unauthorized administrative access</li>



<li>Modify firewall and routing configurations</li>



<li>Create unauthorized accounts</li>



<li>Install or execute malicious scripts</li>



<li>Use compromised routers as part of botnets</li>



<li>Route malicious traffic through compromised devices</li>



<li>Conduct reconnaissance of internal networks</li>



<li>Maintain persistent access to the network</li>
</ul>



<p class="wp-block-paragraph">Because routers sit at a critical point between an organization&#8217;s internal network and the internet, their compromise can have consequences beyond the router itself.</p>



<h2 class="wp-block-heading">Why Internet-Facing MikroTik Routers Are at Risk</h2>



<p class="wp-block-paragraph">The following conditions can significantly increase exposure:</p>



<ol class="wp-block-list">
<li><strong>Outdated RouterOS firmware</strong></li>



<li><strong>Factory-default configurations</strong></li>



<li><strong>Weak or reused administrator passwords</strong></li>



<li><strong>Publicly accessible Winbox</strong></li>



<li><strong>Internet-exposed WebFig/HTTP/HTTPS</strong></li>



<li><strong>Internet-exposed SSH</strong></li>



<li><strong>Unnecessary REST API access</strong></li>



<li><strong>Insecure SNMP configuration</strong></li>



<li><strong>Unknown or unnecessary administrator accounts</strong></li>



<li><strong>Insufficient firewall restrictions</strong></li>



<li><strong>Lack of logging and monitoring</strong></li>
</ol>



<p class="wp-block-paragraph">A router does not necessarily need to be completely outdated to be at risk. An otherwise updated device can still be exposed if its management services are unnecessarily available from the public internet.</p>



<h2 class="wp-block-heading">Common Attack Methods</h2>



<h3 class="wp-block-heading">1. Internet-Wide Scanning</h3>



<p class="wp-block-paragraph">Attackers can automatically scan large numbers of public IP addresses looking for exposed MikroTik management services.</p>



<p class="wp-block-paragraph">Commonly targeted services include:</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Service</th><th>Typical Port</th></tr></thead><tbody><tr><td>Winbox</td><td>TCP 8291</td></tr><tr><td>HTTP</td><td>TCP 80</td></tr><tr><td>HTTPS</td><td>TCP 443</td></tr><tr><td>SSH</td><td>TCP 22</td></tr><tr><td>SNMP</td><td>UDP 161/162</td></tr><tr><td>REST API</td><td>Depends on configuration</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">The important point is that attackers do not necessarily need to know an organization&#8217;s name or network beforehand. Automated tools can discover exposed devices across the internet.</p>



<h3 class="wp-block-heading">2. Credential Brute-Force Attacks</h3>



<p class="wp-block-paragraph">Attackers may repeatedly attempt to authenticate using commonly used or previously compromised passwords.</p>



<p class="wp-block-paragraph">Weak credentials such as:</p>



<ul class="wp-block-list">
<li><code>admin</code></li>



<li><code>123456</code></li>



<li><code>password</code></li>



<li><code>mikrotik</code></li>



<li>Blank/default passwords</li>
</ul>



<p class="wp-block-paragraph">should never be used on an internet-facing network device.</p>



<p class="wp-block-paragraph">Every administrative account should have a <strong>strong, unique password</strong>.</p>



<h3 class="wp-block-heading">3. Exploitation of Vulnerable RouterOS Versions</h3>



<p class="wp-block-paragraph">Older or vulnerable RouterOS releases may contain security weaknesses that attackers can attempt to exploit.</p>



<p class="wp-block-paragraph">Organizations should therefore identify the exact RouterOS version running on every MikroTik device and compare it with the vendor&#8217;s currently supported and security-patched releases.</p>



<p class="wp-block-paragraph">Security teams should verify the applicability of individual vulnerabilities to their specific RouterOS version rather than assuming that every listed vulnerability affects every device.</p>



<h3 class="wp-block-heading">4. Persistence After Compromise</h3>



<p class="wp-block-paragraph">Obtaining initial access may only be the beginning.</p>



<p class="wp-block-paragraph">An attacker who successfully compromises a router may attempt to create additional accounts, modify firewall rules, change routing configurations, create scripts or scheduled tasks, or alter DNS and proxy settings.</p>



<p class="wp-block-paragraph">These changes can allow an attacker to maintain access even after the original vulnerability or password problem has been addressed.</p>



<h2 class="wp-block-heading">Potential Impact of a Compromised MikroTik Router</h2>



<p class="wp-block-paragraph">A compromised router can create several serious security risks.</p>



<h3 class="wp-block-heading">Unauthorized Administrative Access</h3>



<p class="wp-block-paragraph">Attackers may gain privileged access to configuration and management functions.</p>



<h3 class="wp-block-heading">Network Reconnaissance</h3>



<p class="wp-block-paragraph">A compromised router can provide valuable information about internal systems, network routes, services and infrastructure.</p>



<h3 class="wp-block-heading">Botnet Recruitment</h3>



<p class="wp-block-paragraph">The router may be incorporated into a botnet and used for scanning, proxying, denial-of-service activity or other malicious operations.</p>



<h3 class="wp-block-heading">Traffic Proxying</h3>



<p class="wp-block-paragraph">Attackers may route malicious traffic through the compromised device, making it more difficult to identify their actual infrastructure.</p>



<h3 class="wp-block-heading">Credential Compromise</h3>



<p class="wp-block-paragraph">Weak, shared or reused administrative credentials can be compromised through automated attacks.</p>



<h3 class="wp-block-heading">Network Security Bypass</h3>



<p class="wp-block-paragraph">Unauthorized changes to firewall, NAT or routing rules could weaken existing security controls.</p>



<h3 class="wp-block-heading">Service Disruption</h3>



<p class="wp-block-paragraph">Incorrect or malicious configuration changes can interrupt internet connectivity and internal network services.</p>



<h3 class="wp-block-heading">Sensitive Information Exposure</h3>



<p class="wp-block-paragraph">Router configurations can contain information about network topology, addressing, routing and other operational details.</p>



<h3 class="wp-block-heading">Lateral Movement</h3>



<p class="wp-block-paragraph">A compromised router may provide attackers with a strategic position from which to target other systems connected to the network.</p>



<h2 class="wp-block-heading">Security Vulnerabilities That Organizations Should Review</h2>



<p class="wp-block-paragraph">Security teams should check whether their deployed RouterOS versions are affected by publicly reported vulnerabilities, including vulnerabilities associated with:</p>



<ul class="wp-block-list">
<li>Legacy RouterOS branches</li>



<li>REST API endpoints</li>



<li>Winbox account enumeration</li>



<li>Memory corruption</li>



<li>Hotspot-related vulnerabilities</li>
</ul>



<p class="wp-block-paragraph">Examples identified in the advisory material include <strong>CVE-2026-7668, CVE-2025-10948, CVE-2024-54772, CVE-2022-45315 and CVE-2021-3014</strong>.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><strong>Important:</strong> Organizations should verify the affected versions, technical applicability and available vendor fixes for each CVE against their actual RouterOS deployment before taking remediation decisions.</p>
</blockquote>



<h2 class="wp-block-heading">How to Check Whether Your MikroTik Router May Be Exposed</h2>



<p class="wp-block-paragraph">Administrators should review their MikroTik infrastructure for the following warning signs:</p>



<ul class="wp-block-list">
<li>Repeated failed login attempts</li>



<li>Login attempts from unfamiliar external IP addresses</li>



<li>Unexpected successful administrative logins</li>



<li>Unknown administrator accounts</li>



<li>Recently created user accounts</li>



<li>Unexpected firewall-rule changes</li>



<li>Unexpected NAT configuration changes</li>



<li>Unauthorized routing changes</li>



<li>Suspicious RouterOS scripts</li>



<li>Unexpected scheduled tasks</li>



<li>Changes to DNS or proxy configuration</li>



<li>Unusual outbound traffic</li>



<li>Unexpected SNMP activity</li>



<li>Public exposure of management interfaces</li>



<li>Outdated RouterOS versions</li>
</ul>



<p class="wp-block-paragraph">Finding one of these indicators does not automatically prove that a router has been compromised, but it should trigger further investigation.</p>



<h2 class="wp-block-heading">Recommended Security Measures</h2>



<h2 class="wp-block-heading">1. Update RouterOS</h2>



<p class="wp-block-paragraph">Upgrade MikroTik devices to a <strong>current vendor-supported and security-patched RouterOS release</strong> appropriate for the hardware and deployment.</p>



<p class="wp-block-paragraph">Do not continue operating vulnerable legacy firmware simply because the router is functioning normally.</p>



<p class="wp-block-paragraph">For legacy RouterOS v6 devices where continued use is unavoidable and the relevant hardware/software supports it, organizations should apply the appropriate vendor-supported security update and plan migration to a supported release.</p>



<h2 class="wp-block-heading">2. Use Strong and Unique Passwords</h2>



<p class="wp-block-paragraph">Replace all:</p>



<ul class="wp-block-list">
<li>Default passwords</li>



<li>Weak passwords</li>



<li>Shared passwords</li>



<li>Reused passwords</li>



<li>Easily guessable passwords</li>
</ul>



<p class="wp-block-paragraph">Each administrative account should have a strong and unique credential.</p>



<p class="wp-block-paragraph">Where supported, organizations should also use stronger authentication and centralized administrative controls appropriate to their environment.</p>



<h2 class="wp-block-heading">3. Do Not Expose Management Interfaces to Everyone</h2>



<p class="wp-block-paragraph">Management services should not normally be accessible from the entire public internet.</p>



<p class="wp-block-paragraph">Restrict administrative access to trusted networks, VPNs or specifically authorized IP addresses wherever possible.</p>



<p class="wp-block-paragraph">Particular attention should be given to:</p>



<ul class="wp-block-list">
<li>Winbox</li>



<li>WebFig</li>



<li>SSH</li>



<li>REST API</li>



<li>SNMP</li>
</ul>



<p class="wp-block-paragraph">A good security principle is:</p>



<p class="wp-block-paragraph"><strong>If a management service does not need to be reachable from the internet, don&#8217;t expose it to the internet.</strong></p>



<h2 class="wp-block-heading">4. Disable Unnecessary Services</h2>



<p class="wp-block-paragraph">Review all enabled MikroTik services and disable services that are not required.</p>



<p class="wp-block-paragraph">For example, unused legacy management services should not remain enabled simply because they were included in an old configuration.</p>



<p class="wp-block-paragraph">Reducing the number of exposed services reduces the attack surface.</p>



<h2 class="wp-block-heading">5. Strengthen Firewall Rules</h2>



<p class="wp-block-paragraph">Apply restrictive input firewall rules to prevent unauthorized access to router management services.</p>



<p class="wp-block-paragraph">Administrative services should ideally be accessible only from known and trusted management networks.</p>



<h2 class="wp-block-heading">6. Secure SNMP</h2>



<p class="wp-block-paragraph">If SNMP is not required, consider disabling it.</p>



<p class="wp-block-paragraph">If SNMP is required:</p>



<ul class="wp-block-list">
<li>Restrict access to authorized monitoring systems</li>



<li>Replace default community strings</li>



<li>Avoid publicly exposing SNMP</li>



<li>Monitor unexpected SNMP requests</li>
</ul>



<p class="wp-block-paragraph">Default community strings such as <strong>&#8220;public&#8221;</strong> and <strong>&#8220;private&#8221;</strong> should not be used as a security measure.</p>



<h2 class="wp-block-heading">7. Review Router Accounts</h2>



<p class="wp-block-paragraph">Regularly audit all router accounts.</p>



<p class="wp-block-paragraph">Look for:</p>



<ul class="wp-block-list">
<li>Unknown users</li>



<li>Former employees&#8217; accounts</li>



<li>Inactive accounts</li>



<li>Duplicate accounts</li>



<li>Unnecessary administrator privileges</li>
</ul>



<p class="wp-block-paragraph">Remove accounts that are no longer required.</p>



<h2 class="wp-block-heading">8. Review Configuration Integrity</h2>



<p class="wp-block-paragraph">Administrators should compare the current configuration against an approved baseline.</p>



<p class="wp-block-paragraph">Pay particular attention to:</p>



<ul class="wp-block-list">
<li>Firewall rules</li>



<li>NAT rules</li>



<li>Routing tables</li>



<li>DNS settings</li>



<li>Proxy settings</li>



<li>User accounts</li>



<li>RouterOS scripts</li>



<li>Scheduled tasks</li>
</ul>



<p class="wp-block-paragraph">Unexpected changes should be investigated.</p>



<h1 class="wp-block-heading">Monitoring and Detection</h1>



<p class="wp-block-paragraph">Security does not end after patching the router.</p>



<p class="wp-block-paragraph">Organizations should continuously monitor their network infrastructure for suspicious activity.</p>



<p class="wp-block-paragraph">Recommended monitoring includes:</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Monitoring Activity</th><th>What to Look For</th></tr></thead><tbody><tr><td>Authentication</td><td>Repeated failed logins</td></tr><tr><td>Administrative access</td><td>Unusual source IP addresses</td></tr><tr><td>User accounts</td><td>New or modified accounts</td></tr><tr><td>Firewall</td><td>Unexpected rule changes</td></tr><tr><td>NAT</td><td>Unauthorized configuration changes</td></tr><tr><td>Routing</td><td>Unexpected routes</td></tr><tr><td>Scripts</td><td>Unknown or suspicious scripts</td></tr><tr><td>Traffic</td><td>Unusual outbound traffic</td></tr><tr><td>Management services</td><td>Unexpected internet exposure</td></tr><tr><td>SNMP</td><td>Unauthorized access attempts</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">Centralized logging and alerting can significantly improve the ability to detect suspicious activity early.</p>



<h1 class="wp-block-heading">What to Do If You Suspect a Compromise</h1>



<p class="wp-block-paragraph">If a MikroTik router shows signs of unauthorized access, administrators should treat the situation as a potential security incident.</p>



<p class="wp-block-paragraph">Recommended steps include:</p>



<ol class="wp-block-list">
<li><strong>Restrict or isolate the affected router where operationally possible.</strong></li>



<li>Preserve relevant logs and configuration information.</li>



<li>Review all administrator accounts.</li>



<li>Change compromised or potentially exposed credentials.</li>



<li>Review firewall, NAT and routing configurations.</li>



<li>Check RouterOS scripts and scheduled tasks.</li>



<li>Investigate unusual outbound traffic.</li>



<li>Determine whether other systems may have been accessed.</li>



<li>Update the router to a secure supported release.</li>



<li>Rebuild or restore the configuration from a known-good baseline where necessary.</li>



<li>Continue monitoring the device after recovery.</li>
</ol>



<p class="wp-block-paragraph">Simply changing the password may not be sufficient if an attacker has already established persistence through another account, script or configuration change.</p>



<h1 class="wp-block-heading">Security Checklist for MikroTik Administrators</h1>



<figure class="wp-block-image size-full"><img fetchpriority="high" decoding="async" width="1020" height="574" src="https://pk-360.com/wp-content/uploads/2026/09/MikroTik-Router-Security-Protect-Against-Brute-Force-Attacks-2.webp" alt="" class="wp-image-2188" srcset="https://pk-360.com/wp-content/uploads/2026/09/MikroTik-Router-Security-Protect-Against-Brute-Force-Attacks-2.webp 1020w, https://pk-360.com/wp-content/uploads/2026/09/MikroTik-Router-Security-Protect-Against-Brute-Force-Attacks-2-767x432.webp 767w, https://pk-360.com/wp-content/uploads/2026/09/MikroTik-Router-Security-Protect-Against-Brute-Force-Attacks-2-300x169.webp 300w" sizes="(max-width: 1020px) 100vw, 1020px" /></figure>



<p class="wp-block-paragraph">Use the following checklist for every internet-facing MikroTik router:</p>



<ul class="wp-block-list">
<li>RouterOS is updated to a supported security-patched release</li>



<li>Default credentials have been removed</li>



<li>Administrator passwords are strong and unique</li>



<li>Unnecessary administrator accounts have been removed</li>



<li>Winbox is restricted to trusted networks</li>



<li>WebFig is restricted to trusted networks</li>



<li>SSH is restricted to trusted networks</li>



<li>REST API is disabled or properly restricted where applicable</li>



<li>Unnecessary services are disabled</li>



<li>SNMP is disabled if not required</li>



<li>SNMP community strings are not default</li>



<li>Firewall input rules restrict management access</li>



<li>NAT and routing configurations have been reviewed</li>



<li>RouterOS scripts have been reviewed</li>



<li>Scheduled tasks have been reviewed</li>



<li>Authentication logs are monitored</li>



<li>Configuration changes are monitored</li>



<li>Unusual outbound traffic is investigated</li>



<li>A known-good configuration backup is maintained</li>



<li>An incident-response procedure is available</li>
</ul>



<h1 class="wp-block-heading">Final Recommendations</h1>



<p class="wp-block-paragraph">MikroTik routers are an important part of many organizations&#8217; network infrastructure, but they should be treated as <strong>critical security devices</strong>, not simply as internet connectivity equipment.</p>



<p class="wp-block-paragraph">The combination of an outdated RouterOS version, weak credentials and publicly accessible management services can create a significant security risk.</p>



<p class="wp-block-paragraph">Organizations should therefore prioritize:</p>



<p class="wp-block-paragraph"><strong>Patch → Harden → Restrict → Monitor → Respond</strong></p>



<p class="wp-block-paragraph">Updating RouterOS alone is not enough. Security teams should also reduce internet exposure, strengthen authentication, remove unnecessary services and accounts, review configurations and continuously monitor administrative activity.</p>



<p class="wp-block-paragraph">For organizations with internet-facing MikroTik infrastructure, <strong>now is a good time to perform a complete security review rather than waiting for evidence of compromise.</strong></p>



<h3 class="wp-block-heading">Disclaimer</h3>



<p class="wp-block-paragraph">This article is intended for cybersecurity awareness and defensive security purposes. Organizations should verify the technical applicability of vulnerabilities and remediation recommendations against their specific MikroTik hardware, RouterOS version, network architecture and vendor documentation before making changes to production systems.</p>



<ul class="wp-block-social-links is-layout-flex wp-block-social-links-is-layout-flex"></ul>



<h4 class="wp-block-heading has-text-align-center has--font-size">MikroTik Router Security: Protect Against Brute-Force Attacks</h4>



<p class="kt-adv-heading2166_007d62-c8 wp-block-kadence-advancedheading" data-kb-block="kb-adv-heading2166_007d62-c8"></p>
<div class="pvc_clear"></div><p id="pvc_stats_2166" class="pvc_stats all  " data-element-id="2166" style=""><i class="pvc-stats-icon large" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" version="1.0" viewBox="0 0 502 315" preserveAspectRatio="xMidYMid meet"><g transform="translate(0,332) scale(0.1,-0.1)" fill="" stroke="none"><path d="M2394 3279 l-29 -30 -3 -207 c-2 -182 0 -211 15 -242 39 -76 157 -76 196 0 15 31 17 60 15 243 l-3 209 -33 29 c-26 23 -41 29 -80 29 -41 0 -53 -5 -78 -31z"/><path d="M3085 3251 c-45 -19 -58 -50 -96 -229 -47 -217 -49 -260 -13 -295 52 -53 146 -42 177 20 16 31 87 366 87 410 0 70 -86 122 -155 94z"/><path d="M1751 3234 c-13 -9 -29 -31 -37 -50 -12 -29 -10 -49 21 -204 19 -94 39 -189 45 -210 14 -50 54 -80 110 -80 34 0 48 6 76 34 21 21 34 44 34 59 0 14 -18 113 -40 219 -37 178 -43 195 -70 221 -36 32 -101 37 -139 11z"/><path d="M1163 3073 c-36 -7 -73 -59 -73 -102 0 -56 133 -378 171 -413 34 -32 83 -37 129 -13 70 36 67 87 -16 290 -86 209 -89 214 -129 231 -35 14 -42 15 -82 7z"/><path d="M3689 3066 c-15 -9 -33 -30 -42 -48 -48 -103 -147 -355 -147 -375 0 -98 131 -148 192 -74 13 15 57 108 97 206 80 196 84 226 37 273 -30 30 -99 39 -137 18z"/><path d="M583 2784 c-38 -19 -67 -74 -58 -113 9 -42 211 -354 242 -373 16 -10 45 -18 66 -18 51 0 107 52 107 100 0 39 -1 41 -124 234 -80 126 -108 162 -133 173 -41 17 -61 16 -100 -3z"/><path d="M4250 2784 c-14 -9 -74 -91 -133 -183 -95 -150 -107 -173 -107 -213 0 -55 33 -94 87 -104 67 -13 90 8 211 198 130 202 137 225 78 284 -27 27 -42 34 -72 34 -22 0 -50 -8 -64 -16z"/><path d="M2275 2693 c-553 -48 -1095 -270 -1585 -649 -135 -104 -459 -423 -483 -476 -23 -49 -22 -139 2 -186 73 -142 361 -457 571 -626 285 -228 642 -407 990 -497 242 -63 336 -73 660 -74 310 0 370 5 595 52 535 111 1045 392 1455 803 122 121 250 273 275 326 19 41 19 137 0 174 -41 79 -309 363 -465 492 -447 370 -946 591 -1479 653 -113 14 -422 18 -536 8z m395 -428 c171 -34 330 -124 456 -258 112 -119 167 -219 211 -378 27 -96 24 -300 -5 -401 -72 -255 -236 -447 -474 -557 -132 -62 -201 -76 -368 -76 -167 0 -236 14 -368 76 -213 98 -373 271 -451 485 -162 444 86 934 547 1084 153 49 292 57 452 25z m909 -232 c222 -123 408 -262 593 -441 76 -74 138 -139 138 -144 0 -16 -233 -242 -330 -319 -155 -123 -309 -223 -461 -299 l-81 -41 32 46 c18 26 49 83 70 128 143 306 141 649 -6 957 -25 52 -61 116 -79 142 l-34 47 45 -20 c26 -10 76 -36 113 -56z m-2057 25 c-40 -58 -105 -190 -130 -263 -110 -324 -59 -707 132 -981 25 -35 42 -64 37 -64 -19 0 -241 119 -326 174 -188 122 -406 314 -532 468 l-58 71 108 103 c185 178 428 349 672 473 66 33 121 60 123 61 2 0 -10 -19 -26 -42z"/><path d="M2375 1950 c-198 -44 -350 -190 -395 -379 -18 -76 -8 -221 19 -290 114 -284 457 -406 731 -260 98 52 188 154 231 260 27 69 37 214 19 290 -38 163 -166 304 -326 360 -67 23 -215 33 -279 19z"/></g></svg></i> <img decoding="async" width="16" height="16" alt="Loading" src="https://pk-360.com/wp-content/plugins/page-views-count/ajax-loader-2x.gif" border=0 /></p><div class="pvc_clear"></div>]]></content:encoded>
					
					<wfw:commentRss>https://pk-360.com/mikrotik-router-security-alert/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
