16 ms·
MikroTik routers are forwarding owners’ traffic to unknown attackers
- a012 8y agoArticle link is down on my end.
- ccnafr 8y agoIt's basically another take on this older report: https://www.trustwave.com/Resources/SpiderLabs-Blog/Mass-MikroTik-Router-Infection-%E2%80%93-First-we-cryptojack-Brazil,-then-we-take-the-World-/ https://www.trustwave.com/Resources/SpiderLabs-Blog/Mass-Mik...
- appleflaxen 8y agothat's a month old; has the compromise been going on that long? i guess so...
- 24gttghh 8y agoIt's been occurring since at least March I think? https://blog.mikrotik.com/security/winbox-vulnerability.html https://blog.mikrotik.com/security/winbox-vulnerability.html https://forum.mikrotik.com/viewtopic.php?f=21&t=137572 https://forum.mikrotik.com/viewtopic.php?f=21&t=137572
- ccnafr 8y agoNo. That's when the vulnerability was discovered. The cryptojacking attacks on routers began a month ago. Qihoo is just reporting on an ongoing campaign. But I didn't see anything different from the Trustwave report, except that attackers misconfigured some routers to send traffic into a blackhole for some reason.
- deleted 8y ago[deleted]
- burkesquires 8y agoDo NOT visit...trojan at URL!
- isostatic 8y agoReally? In what way?
- breakingcups 8y agoI (ironically) got a CoinHive warning from TrendMicro.
- deleted 8y ago[deleted]
- fasafsafsf 8y agoGet a better antivirus then, because it's picking the URL that appears in the post.
- burkesquires 8y agoMy antivirus software found two trojans and immediately raised a warning.
- JohnnyWesh 8y agoI think u use Mikrotik without an update! =D
- burkesquires 8y agoThat stinks. I tried to help the community by providing a warning and I get downvoted. What is the motivation to help? From now on I will not issue any warnings.
- isostatic 8y agoMy home router has the following /ip firewall filter add action=accept chain=input connection-state=established add action=accept chain=input connection-state=related add action=accept chain=input dst-port=5000 protocol=udp add action=accept chain=input dst-port=6000 protocol=udp add action=accept chain=input dst-port=6001 protocol=udp add action=accept chain=input protocol=icmp add action=accept chain=input dst-port=22 protocol=tcp src-address-list=Mgmt add action=accept chain=input dst-port=179 in-interface-list=LAN protocol=tcp add action=drop chain=input in-interface=btopenreach add action=drop chain=input Clearly it's possible that an attacker could come in from the back door (desktop, XSS etc), I could lock down the BGP more, and tighen up Mgmt beyond it's current fairly wide subnets (a /16 owned by work and my wired range), but it becomes a hassle, which leads to more disabling of the "action=drop" while debugging. My backup script emails me when the configuration changes To check if your proxy is enabled (probably shouldn't be) /ip proxy print enabled: no
- dboreham 8y agoAlso change the winbox port if you need it to be enabled.
- jessaustin 8y agoThat's a way not to be the low-hanging fruit, but if someone wants this port they're going to find it.
- dboreham 8y agoOf course. But the attack mentioned above looks to have simply targeted the default port. Ideally : use a non-default port, and source-IP-based firewalling, and keep firmware up to date.
- 24gttghh 8y agoYou could limit only certain ICMP types as well, and change your SSH port. And you can ask yourself: Do I really need access to my firewall from work?
- JohnnyWesh 8y agoJust yesterday updated my Mikrotik to latest current. And now read that news. Great!
- teilo 8y agoThen you're just fine. The vulnerabilities were patched months ago.
- kibwen 8y agoCan anyone suggest a wireless router that someone can buy today that either ships with or can be flashed with OSS firmware? I've been trying to shop around for one compatible with DD-WRT or OpenWRT and been rather disheartened so far; every promising model I've found either requires you to play roulette with the specific hardware version of the router that you receive (which is never advertised on product pages), or is out of stock entirely, or costs upwards of $250 (which is tough to sell to my friends, when their ISP charges $10/mo to rent a router with much less hassle).
- Ahl4Gom6 8y agoI'm running openwrt on an R7800 and so far had no issues. But that's just the router, you'll still need a modem.
- ajayh 8y agoMaybe something like the PC Engines apu2? http://www.pcengines.ch/apu2.htm http://www.pcengines.ch/apu2.htm x86, can run OpenWRT.
- LambdaComplex 8y agoI'm currently using an apu4b4 running OpenBSD as a router; it's been a good way to (as a Linux guy) dip my feet into the BSD ecosystem. Later today (if all goes well) I'll be adding wifi to it!
- mrsteveman1 8y agoI have an APU2 and it's really the perfect router for any small office or house. Intel NICs, plenty of ram and an mSATA port make it quite capable. I have pfSense on it at the moment, which works very well. At one point I had an 802.11n card in my older ALIX2D router, but there were stability and performance issues so now I always use a separate access point, most recently a Unifi AC-PRO which has some quirks but works well in general. I've been happy enough with the x86 routing strategy that when it came time to replace my older Cisco 100mbps switch, I decided to do that with x86 hardware as well. All of the smaller/cheaper gigabit switches either didn't support VLANs, made way too much heat, or had reliability issues, and the ones that were suitable were quite expensive and had reliability issues of their own. So, I found a Supermicro Atom C2000 board (A1SRM-LN7F[1]) on sale for $90, which has 7 Intel NIC gigabit ports built-in and supports ECC ram. I put it in a Supermicro 1U[2] enclosure along with an Intel PCIe 4x gigabit NIC, for a total of 11 gigabit ports on the switch. I installed Debian on it and set up open-vswitch, which worked but was soon replaced by "vlan-aware" Linux bridging. It's easily capable of switching gigabit traffic between multiple machines at the same time, ping shows an average latency of 0.310ms, has very low power usage and makes very little heat. Note that those C2000 Atoms do have a "sudden death" hardware flaw, but Supermicro should have fixed it on more recent inventory, and they will send a "patched" board to replace any that are affected before they fail. The Atom C3000 doesn't have that issue, but I don't think Supermicro (or anyone, really) make any C3000 boards with that many built-in gigabit ports. [1] http://www.supermicro.com/products/motherboard/Atom/X10/A1SRM-LN7F-2358.cfm http://www.supermicro.com/products/motherboard/Atom/X10/A1SR... [2] http://www.supermicro.com/products/chassis/1U/510/SC510T-203B http://www.supermicro.com/products/chassis/1U/510/SC510T-203...
- orf 8y agoCached: https://webcache.googleusercontent.com/search?q=cache:sYLtFjkodtgJ:blog.netlab.360.com/7500-mikrotik-routers-are-forwarding-owners-traffic-to-the-attackers-how-is-yours-en/+&cd=1&hl=en&ct=clnk&gl=pt https://webcache.googleusercontent.com/search?q=cache:sYLtFj...
- TeMPOraL 8y ago> After enabling the Mikrotik RouterOS HTTP proxy, the attacker uses a trick in the configuration by redirecting all the HTTP proxy requests to a local HTTP 403 error page, and in this error page a link for web mining code from coinhive.com is inserted. By doing this, the attacker hopes to perform web mining for all the proxy traffic on the users’ devices > What is disappointing for the attacker though, the mining code does not work in this way, because all the external web resources, including those from coinhive.com necessary for web mining, are blocked by the proxy ACLs set by attackers themselves. Smart enough to breach Mikrotik routers. Dumb enough to fuck up linking in coinhive JS. That screams "script kiddie buying delivery method on an open market". Also, how is coinhive still a thing?
- ballenf 8y ago> Also, how is coinhive still a thing? It's too bad coinhive is so easy to abuse. I'd much rather live in a world where websites are financed with my electric bill rather than my data.
- Kalium 8y agoAny system that enables payments uncoupled from identity - or customer service - over the internet is going to be prone to abuse. Bad money pushes out good money, and paying with someone else's electric bill is always cheaper than paying with yours. Which is to say that pretty much any form of cryptocurrency is likely to stay abuse-prone. Practically speaking, the amount of electric bill you'd have to pay to make up the costs of what your currently pay for with data would almost certainly be shocking. I can't imagine that it costs anything like $5 to mine $5 worth of Monero on your average computer in the first world. And that would be just enough to pay for Gmail, never mind everything else!
- uberswe 8y agoOn an average computer it would take weeks or months to mine $5 worth of Monero but it is doable.
- paul7986 8y agoCurious is this the VPNFilter malware or some new router virus? Lately I’ve been having IP & Internet issues like.... - match suddenly banned me as a subscriber to okcupid and match. They won’t tell me why either & ive been a subscriber on/off for years. Never or ever would I do anything inappropriate though my match.com account I feel was hacked. Yet they don’t want to listen :-( - my 6 month old roku device suddenly would no longer find my router. - yesterday just bought a new Roku & was unable to activate it after many attempts. Anyone else having weird Internet/IP device issues too?
- hrudham 8y agoMy MikroTik started going nuts late last week; it managed to upload ~90Gb worth of data in 3 days (downloads weren't nearly as bad). Considering I only have a 300Gb cap, that hurt. I subsequently re-flashed it, and secured it properly this time, which solved the issue. Using the hardware reset button doesn't fix things, so heads up for others in that situation. Use MikroTik's NetInstall to re-install RouterOS instead.
- justinclift 8y ago> Attackers mainly interested in port 20, 21, 25, 110, and 143, corresponding to FTP-data, FTP, SMTP, POP3, and IMAP traffic. That strongly suggests password harvesting. Those ports/protocols often (not always) are used for unencrypted user/pass combinations. :(
- dboreham 8y agobtw this is the actual vulnerability (since MT release logs do not mention the CVE cited in the article): https://blog.mikrotik.com/security/winbox-vulnerability.html https://blog.mikrotik.com/security/winbox-vulnerability.html (referenced here : https://forum.mikrotik.com/viewtopic.php?f=21&t=137284&start=50#p683938 https://forum.mikrotik.com/viewtopic.php?f=21&t=137284&start...)
- baybal2 8y ago>MikroTik is a Lithuanian company founded in 1996 to develop routers and wireless ISP systems. Mikrotik is Latvian, not Lithuanian.
- r1ch 8y agoIt's worth pointing out that the default configuration of almost every Mikrotik router these days comes with a firewall that blocks inbound access to all ports. Admins have to go out of their way to expose winbox to the internet (as many did - including myself - under the belief the protocol was somewhat secure running over TLS). Unfortunately NIH syndrome runs at an all time high at Mikrotik. Even the RouterOS webserver and SMB implementations were custom written, and both were later found to contain remotely exploitable bugs. I'm sure there are other holes lurking in their implementations of ipsec, openvpn, etc, so I no longer open up anything and rely on port forwarding to more secure and battle-tested services like OpenSSH / Wireguard for remote management.
- eps 8y agoThis explains a lot. Mikrotik boxes are really quirky. They basically have user-facing bugs, symptoms of which can have no explanation except for them fronting some massive clusterfuck on the inside. They used to do bizarre things with timestamps of freshly copied files, when the modified time would oscillate around some convergence point. Some wierd directory names (like .popup ?) were reserved for no apparent reason and an attempt to create them failed with "file not found". That sort of thing. And we even didn't own any of their devices, we were just in a splatter zone from our clients constantly walking into Mikrotik issues. It was few years ago though, so perhaps things have improved since then.
- r1ch 8y agoI've been using MT gear for about 10 years now. I actually think the devices themselves are very solid once they're up and running. I've had some running for years without any issues (try that with most other SOHO router brands!), though reboots are much more frequent these days due to security updates. I do agree though that the software side of things can be a bit quirky and the recent security issues are a worrying glimpse into the quality of their code. In general I wish the platform was more open (you can't even get a shell without rooting the device), but it's something I can live with at this price point. Unfortunately given their affordability and feature set, Mikrotik routers are often times administered by people who don't really have a solid grasp of networking. I've seen some downright awful advice posted on their user forums over the years, stuff that could easily cause connectivity issues under the right circumstances. Who knows how much of that gets copy/pasted into configs after a quick Google search.
- jessaustin 8y agoI always disable winbox on installation. /ip service disable winbox Why would anyone want to use that? My theory is that it has something to do with how in many cases the MT sshd has to be told to figure out the terminal: $ ssh user+t@192.168.88.1 ...and this information is really hard to find. If the terminal settings aren't right and you can't fix them, ssh is unusable and you're stuck with either winbox or webfig. Fortunately, if the ssh session is wrapped in a mosh session then mosh will handle MT's terminal settings.
- 4ad 8y agoAfaik winbox is the only way to reconfigure the device in case of serious IP misconfiguration, or if layer 3 networking does not work for some reason (I just had to debug a switching loop...), as winbox can connect by MAC, rather than IP.
- jessaustin 8y agoIn such a situation I would probably hard reset and upload a saved configuration... certainly not ideal.
- 4ad 8y agoMy equipment is hidden in walls and hard to reset. However, in this case, the problem was at the physical layer, not software configuration, so a reset would not have accomplished anything. Since I do not use Windows, I had to emulate Winbox in Wine... pretty awful experience, but in the end it worked while everything else failed. I would just prefer some sort of unix tool that ssh can use to connect to the equipment through layer 2.