Slashdot Mirror
New SMB Worm Uses Seven NSA Hacking Tools. WannaCry Used Just Two (bleepingcomputer.com)
An anonymous reader writes: Researchers have detected a new worm that is spreading via SMB, but unlike the worm component of the WannaCry ransomware, this one is using seven NSA tools instead of two. Named EternalRocks, the worm seems to be in a phase where it is infecting victims and building its botnet, but not delivering any malware payload.
EternalRocks is far more complex than WannaCry's SMB worm. For starters, it uses a delayed installation process that waits 24 hours before completing the install, as a way to evade sandbox environments. Further, the worm also uses the exact same filenames as WannaCry in an attempt to fool researchers of its true origin, a reason why the worm has evaded researchers almost all week, despite the attention WannaCry payloads have received.
Last but not least, the worm does not have a killswitch domain, which means the worm can't be stopped unless its author desires so. Because of the way it was designed, it is trivial for the worm's owner to deliver any type of malware to any of the infected computers. Unfortunately, because of the way he used the DOUBLEPULSAR implant, one of the seven NSA hacking tools, other attackers can hijack its botnet and deliver their own malware as well. IOCs are available in a GitHub repo.
Ars Technica quotes security researchers who say "there are at least three different groups that have been leveraging the NSA exploit to infect enterprise networks since late April... These attacks demonstrate that many endpoints may still be compromised despite having installed the latest security patch."
EternalRocks is far more complex than WannaCry's SMB worm. For starters, it uses a delayed installation process that waits 24 hours before completing the install, as a way to evade sandbox environments. Further, the worm also uses the exact same filenames as WannaCry in an attempt to fool researchers of its true origin, a reason why the worm has evaded researchers almost all week, despite the attention WannaCry payloads have received.
Last but not least, the worm does not have a killswitch domain, which means the worm can't be stopped unless its author desires so. Because of the way it was designed, it is trivial for the worm's owner to deliver any type of malware to any of the infected computers. Unfortunately, because of the way he used the DOUBLEPULSAR implant, one of the seven NSA hacking tools, other attackers can hijack its botnet and deliver their own malware as well. IOCs are available in a GitHub repo.
Ars Technica quotes security researchers who say "there are at least three different groups that have been leveraging the NSA exploit to infect enterprise networks since late April... These attacks demonstrate that many endpoints may still be compromised despite having installed the latest security patch."
Your computer have virus.
Just look at Google. Terrifying, just terrifying.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
Be sure to spin rhetoric about "NSA" and "CIA" freakouts harder than the actual technical details, as usual!
NSA don't need to craft anything. They just have to read the memo from Microsoft to catch up on where the backdoor was moved to.
Why? Is there not enough information to fill the 24 hour news cycle with Trump in the US, Erdogan in Turkey, the Brexit in Europe, ad infinitum...
Or, and I don't have the tinfoil hat on but it's out of the drawer, will these be used to somehow shunt internet freedoms as the powers that be protect us from another Boogeyman.
Happiness in intelligent people is the rarest thing I know.
Ernest Hemingway
Why has the NSA, who know exactly what weaponized exploits were broadcast to the world. . . Why has the NSA not offered-up any antidotes to their now-public weaponization of a bunch of sploits?
They could swoop in and try to look like the hero here, but there's been no sign of that. Not a peep from the NSA.
Are they just making popcorn and watching the fallout because they think they are computer GODS, enjoying watching the plebes fight all of these forthcoming worms and trojans just to get themselves off before going back to work reducing the security of the USA by continuing to develop more of the same?
No.
I don't read your sig. Why are you reading mine?
Make commercial software companies legally liable.
If you haven't looked into it yet and you're running Windows 7 and above, disable SMB v.1 on Windows as server or client. There's not much reason to maintain it unless you have older hardware/software that relies on it (XP, Windows Server 2003). v.1 is slower and completely replaced by SMB v.2 and v.3.
Wakey wakey sleepyhead....
When the NSA realized that the code had been stolen & likely to be released, they communicated the SMB bug to Microsoft who then released patches for their "maintained" OS's two months ago. It is because of this that they were able to release patches for their out of maintenance OSes as soon as Wannacry started spreading.
Did you just imply that if the NSA said "here's a patch, please apply it globally" that you would apply it blindly?!? I'm not one of the people calling for the NSA to be the world's beta testing organization by buying up all the bugs on the internet & then handing them off to makers so that they patch their code, but even I wouldn't apply a NSA patch blindly like that.
The NSA is not Trump with hourly Twitter updates direct from them to the world. They'll always communicate through proxies.
Democracy is a sheep and two wolves deciding what to have for lunch. Freedom is a well armed sheep contesting the issue
Or everybody could just quit panicking and patch their systems.
Every time another "ogodtheskyisfalling" article comes out covering a new/improved malware based on the leaked NSA toolbox I'm looking for a quick summary early in the article that says "this beastie will be a problem for Windows, probably Win7 and earlier; will not be a problem for Linux; probably won't be a problem for OS X." Or even a simple 0-10 ranking of "no problemo" to "burn your computer NOW!" for each of the three major platforms placed somewhere prominent in the article would be nice. For my less-techie friends/relatives who get all hyped up with every new WormKillerTorpedoBot_Comrade exploit, it could give them an idea if they should be worried and figure out what to do, or not. For me, I can avoid reading pages and pages of turgid tech-prose about something that, not running anything on Windows, I don't need to care about. So how about it Tech Pundits of America, how about a little help here?
for the system to be infected then take them over from the virus writers discretely
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
What goes around is apparently coming around - thanks a lot for that.
Seems that whole "(our) security through (your) obscurity" thing has a few wrinkles in it.
Sincerely,
The people you're supposed to be protecting.
It must have been something you assimilated. . . .
TCP port 137, 139, and 445 are blocked, UDP ports 137 and 138 are blocked. So am I safe?
I've got a printer and NAS on my network, I know the printer uses SMB but not sure of the NAS.
Or everybody could just quit panicking and patch their systems.
I tried.
I downloaded MS17-010 for 64 bit Win 7 (which I run in my work laptop), and after churning for a few mins, it said that the Update Wasn't Installed.
So I simply disabled SMB1 and am hoping for the best.
If anyone has any ideas, I'd love to hear them!
Ned Pyle and others have eloquently described why everyone should drop SMB1 support, yet NAS suppliers and Sonos continue to ship products that use SMB1.
Despite being deprecated by MSFT for years, SMB1 is alive and well with Sonos. There is no SMB2+ support, there is no timeline nor any commitment to add SMB2+ support. Please note: this issue only affects those that use Sonos with a local file server such as a NAS, your PC, etc. to store the music library and then make it accessible via the LAN.
I don't understand how a company that prides itself on making premium audio products doesn't put security ahead of other software development priorities. One juicy scandal can cause way more damage than the modest cost of implementing readily-available SMB2-3.11 server/client software packages.
SMB1 support on the Sonos, if allowed at all, should be on a opt-in basis, with adequate warnings to consumers re: potential pitfalls. Modern incarnations of SMB servers have NTLM v1 and SMB1 support turned off by default for a reason.
Years ago, hackers leveraged Google alerts to find JBOSS servers on the Internet so they could be hacked. Hard to detect these things.
some talented hacker will turn their attention to wiping out all records of student loans and consumer debt. Heck, maybe even mortgages.
We can only hope...
Depends what the staging server was used for and what was found in the wild. Everything or just Windows?
Domestic spying is now "Benign Information Gathering"
If you only followed the news in the past month, you'd notice that Windows vulnerabilities and attack tools were only dumped just after Linux/Solaris/MacOS/Android exploit tools were released by the same group, ShadowBrokers.
Are these posters active in the workforce? Every relevant office in the world uses windows.
{...} But out here in the functional world, windows is everywhere.
Depends of the field you work.
Academic research ?
Specially in fields like computational biology ?
It's going to be exclusively UNIX.
With Mac OS X being a bit more popular on the laptops and workstations of the researchers,
and Linux having monopoly on the servers and compute nodes.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
They are an enemy of the United States. Arrest them and take their computers.
Corporatism != Free Market
That's great advice but see my note below, if you want to run a Sonos from a file server as intended, you have to have SMB1 (NT1) enabled on that file server, which means also enabling NTLM v1 authentication.
Yes, there is a complicated workaround by using Plex or subsonic as a means of feeding the Sonos data without the need for SMB1 insecurity, but implementing this system is not the faint of heart. Plus, with every new service enabled on the server, you add more potential exploits.
All I want is to be able to enable SMB 3+ on my home file server or shut it off altogether. Presently, the best solution may be to use a burner file server just for the Sonos with one-way updates. Nuts!
I'm not familiar with this product or Sonos but this sounds proprietary.
Not reimplementing any part of the product is more profitable and most computer users are non-technical so they don't understand what SMB is let alone which revision is known to be insecure. Users should be advised to liberate themselves from Sonos' control over the user's computers; seek other ways to play the audio, ways that respect a user's freedom to run, modify, and share (including commercially). Perhaps reconsider Sonos if they distribute products that respect a user's software freedom. After all, if the security issues you describe are important enough that should be sufficient justification to seek the freedoms you deserve with or without Sonos' help.
Digital Citizen
Disabling SMB1 is not enough to stop the EternalRocks worm, which includes the EternalChampion (SMB2) and EternalSynergy (SMB3) exploits.
Disabling SMB1 is not enough to stop the EternalRocks worm, which includes the EternalChampion (SMB2) and EternalSynergy (SMB3) exploits.
Have I mentioned that I hate Windows?