'Slingshot' Malware That Hid For Six Years Spread Through Routers
An anonymous reader quotes a report from Engadget: Security researchers at Kaspersky Lab have discovered what's likely to be another state-sponsored malware strain, and this one is more advanced than most. Nicknamed Slingshot, the code spies on PCs through a multi-layer attack that targets MikroTik routers. It first replaces a library file with a malicious version that downloads other malicious components, and then launches a clever two-pronged attack on the computers themselves. One, Canhadr, runs low-level kernel code that effectively gives the intruder free rein, including deep access to storage and memory; the other, GollumApp, focuses on the user level and includes code to coordinate efforts, manage the file system and keep the malware alive. Kaspersky describes these two elements as "masterpieces," and for good reason. For one, it's no mean feat to run hostile kernel code without crashes. Slingshot also stores its malware files in an encrypted virtual file system, encrypts every text string in its modules, calls services directly (to avoid tripping security software checks) and even shuts components down when forensic tools are active. If there's a common method of detecting malware or identifying its behavior, Slingshot likely has a defense against it. It's no wonder that the code has been active since at least 2012 -- no one knew it was there. Recent MikroTik router firmware updates should fix the issue. However, there's concern that other router makers might be affected.
Over that time you or someone using your wireless network has installed dozens of apps that has been legally spying on and selling your data to anyone will pay a few cents.
Why can we not find these assholes, and publically hang them? And leave them dangling for a while for all to see. They are poisoning the well - this is not cute hacker fun. This is, and has been, very serious. And nothing seems to be done about it.
And them damn Rushers. Again!
This is just the latest of a number of state sponsored attacks that Kaspersky has published details on. They are doing fantastic work.
Whatever your view on the level of the cooperation with the Russian state, exposing these sophisticated attacks and attack vectors makes us all safer.
Which forensic tools should I keep active in order to have those viruses conveniently shut down components while they think I am a researcher looking for them? :D
The article doesn't call out what versions are affected. My router has 6.40.3 and an upgrade command says that's the latest.
But the bigger problem I have is: (from the TFA)
Routers download and run various DLL files in the normal course of business.
WTF? No they don't. My router doesn't download and run anything during normal operation and it doesn't need to and shouldn't need to. During an upgrade sure.
Anyone who installs a router that downloads stuff and runs it without their express command to do so is simply asking for it.
On top of that I don't understand why they call out DLLs. Mikrotiks run RouterOS based on Linux, most of which don't use DLLs for anything.
pretty much guarantees it wasn't made in Amercia. Where the attitude is code correctly why that eats in to the bottom line - shove it out the door lt the users find the bugs.
"If there's a common method of detecting malware or identifying its behavior, Slingshot likely has a defense against it."
Unplug all computers from the router and see if the router is still trying to broadcast out by watching the blinking lights (assuming they are even present.)
Can almost guarantee they didn't bother thinking about old-fashioned forensics.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
And because your happiness is worth more to you than EVERYONE ELSE'S FREEDOMS you invite and welcome slavery.
Fuck you buddy.
It really looks good on you and makes your NSA sponsored crap so much more believable.
An engadget story linking to ArsTechnica, linking to Kaspersky
How can we trust a firmware update to reliably clean up an infected device? After all, the firmware update would need to be installed by the currently running infected firmware. Couldn't the current firmware infect the new firmware as its being installed? Sounds like we might need to JTAG a new image straight to the hardware.
The routers need to be treated like any other compromised IoT device: Physically thrown away, and replaced by a known good brand, perhaps something running PFSense on a small scale.
I don't think a known good brand exists.
WTF? No they don't. My router doesn't download and run anything during normal operation and it doesn't need to and shouldn't need to.
Maybe your own doesn't.
But lots of equipment provided to client by telco (the router that you received for free when you signed up for DSL/cable/fibre internet) do.
In the name of user-friendliness, defined as "my grand-ma is unable to upgrade the firmware nor even configure the settings, so everybody is imposed auto-updates", nearly all of these device download and run a ton of shit.
It might be just scripts (to set or update configuration) or it might be complete firmware upgrade (including telco's own "optimisation" - you tauch preloaded crapware waws limited to desktops?)
cue in rant by RMS about "autoupdate being a form of remote execution and thus security danger".
Anyone who installs a router that downloads stuff and runs it without their express command to do so is simply asking for it.
Sadly that's a situation that is enforced by telco on unsuspecting users.
You got to get out of your way to buy your own personnal router, disable it's auto-update/auto-configuration capabilities, plug it in and manually configure it and upgrade it to a known good firmware (preferably something from OpenWrt/LEDE if you decide not to trust the original equipement manufacturer.
On top of that I don't understand why they call out DLLs. Mikrotiks run RouterOS based on Linux, most of which don't use DLLs for anything.
As pointed out by other, in this case it's the administration software that downloads Windows DLLs from the router and runs them on the admin's PC.
But all the rants about auto-update and remote execution still apply in this context too.
And it's not new at all. Microsoft SMB/CIFS "shared printers" provide drivers on the servers. A client Windows system that wants to send documents on a server print queue will also automatically download and run printer drivers in the exact same fashion.
(But yeah, in this case, it's not the RouterOS itself loading .so and .ko and running them without any user approval).
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
My listing for this is years out of date, but is it still the case that the only modern flash drives with hardware write protection are from Kanguru, a few models of PQI, and maybe 1-2 Imation devices?
Do you allow devices like the secured IODD/Zalman drive enclosures that can be set up for read-only access as well?
fencepost
just a little off
My ISP requires these devices for their sort of frame relay tunnel thing they got going. I have not been able to replicate that connection on pfsense. So i have a mikrotik router that i own, sitting infront of my pfsense on the wan side.
Yikes. gonna patch it tonight when i get home! thing cost like $100 bucks so i am not going to throw it away. i did restrict all access to it externally, so hopefully whatever mikrotik exploit this is requires some sort of port to be open to work...
ah found some info. it seems to have only infected africa and middle east and uses copies the dll to a windows machine when you use winbox to configure. I do remember using winbox at some point but i think it didnt work very well. still scarily close to home!
https://s3-eu-west-1.amazonaws...
Since when is PFSense good? Ive cleaned up more infected PFS boxes then MT's. So a bunch of people left things open. MT changed all this a year ago. Its no longer a issue and anyone still running year old code without a firewall is getting what they are asking for.
Just SSH in and update. You have much larger attack surface running windows or letting people visit your wireless.