CIA Malware Can Switch Clean Files With Malware When You Download Them Via SMB (bleepingcomputer.com)
An anonymous reader quotes a report from Bleeping Computer: "After taking last week off, WikiLeaks came back today and released documentation on another CIA cyber weapon. Codenamed Pandemic, this is a tool that targets computers with shared folders, from where users download files via SMB. The way Pandemic works is quite ingenious and original, and something not seen before in any other malware strain. According to a leaked CIA manual, Pandemic is installed on target machines as a "file system filter driver." This driver's function is to listen to SMB traffic and detect attempts from other users to download shared files from the infected computer. Pandemic will intercept this SMB request and answer on behalf of the infected computer. Instead of the legitimate file, Pandemic will deliver a malware-infected file instead. According to the CIA manual, Pandemic can replace up to 20 legitimate files at a time, with a maximum size of 800MB per file, and only takes 15 seconds to install. Support is included for replacing both 32-bit and 64-bit files. The tool was specifically developed to replace executable files, especially those hosted on enterprise networks via shared folders. The role of this cyber weapon is to infect corporate file sharing servers and deliver a malicious executable to other persons on the network, hence the tool's name of Pandemic.
...But can it get into Madagascar after they've closed their port?!
An Luigi, too!
This first post brought to you by the Super Mario Brothers.
Not every permutation and combination of malware not seen before is "ingenious".
File system filter driver dynamically installs malware. Got it. Isn't this the kind of thing a file system filter driver is supposed to do? "filter can mean log, observe, modify...." https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/what-is-a-file-system-filter-driver-
Handy tool, but unless I'm missing something, "ingenious" is way overstated. 25 years ago, this might have been novel.
It is a disservice to Slashdot readers when the post fails to mention the operating systems affected by the exploit. Is this Windows only? Samba runs on Mac and Linux. Does the malware affect them, or does the executable bit get in the way?
I thought this was about a vulnerability in Super Monkey Ball.
SMB sucks ass? and now it's revealed to be seriously insecure as well?... now there's a couple of newsflashes that will shock the entire tech industry to it's core
Who "downloads" with SMB. SMB is a distributed file system like NFS isn't it. transferring files on an intranet is not what we conventionally mean by "download". The latter usually implies the importation of file from the internet not a local net. It's misleading to conflate these as one usually has quite different procedures in the security onion for treating these two cases.
Some drink at the fountain of knowledge. Others just gargle.
They are sure making NFS look like a more attractive file sharing protocol than SMB these days.
(though I have seen some pretty shocking NFS exploits)
Support is included for replacing both 32-bit and 64-bit files
Whew! All the files on my disk are 8-bit files.
I know, because I look at them with od -t x1. As long as I stay away from od -t x4 or x8, I should be safe.
Want to know why the simplest security methods are missing from Windows, Linux, etc? Look to Truecrypt for an explanation...
Truecrypt ***is*** the de facto method to ensure your files are properly encrypted, and this posed the greatest problen to the NSA/GCHQ/CIA/Google. The 'maths' of Truecrypt couldn't be disputed so social engineering was used instead. Key members of the team were paid millions by the US government to FUD their own project to 'death' in the eyes of the more naive. The main tech sites, and neo-liberal outlets like this one, pushed the FUD, til the dumb-dumbs lost confidence in the software. Then of course, the Truecrypt team refused to move the project to Win10.
File operating systems could have proper checksum/file signature methods where the integraty of a file across the chain of file movement was an inate part of the system. But the very opposite is true. Only recently, using a very old wireless dongle on a new Win10 build, fauly dongle drivers meant SMD file transfers to the new machine were silently corrupting the copied files. The data integrity tests in one of the many transport layers involved were silently failing. Imagine the scope for corporate disaster if such a fault was happening to back-ups.
But why doesn't Win10 (the nth version of NT) do something as basic as properly checksum files/file chunks as the data moves? Because the NSA needs backdoors and flaws in every major computer system, and robust data integrity and robust data encryption is death to NSA spying methods.
Microsoft is broken by design- and actually gets more broken year by year. A metric ton of Linux devs are on the payroll of the NSA and GCHQ. And so the simplest request for the simplest improvemnts to closed and open-source software in bug forums gets mocked and ignored by 'devs'.
Of course third party tools (like Truecrypt even today) can get the job done, but their poor integration with the OS makes their use less than ideal, and certainly less than convenient. And we have to suffer possible file corruption across the chain of movement on our devices just so there are 'chinks' into which the NSA can insert their dirty hands when they wish- and this is just plain evil.
Dr. Evil,
I'm guessing you are a saint compared to the evil of the CIA.
I wish the U.S. had a healthy government.
This was conceived of during the WfW3.11 era. Never got around to actually developing but it's so nice somebody actually did so.
Good job!
I can tick this off my todo list now.
What the hell is a "32 bit file"? What the hell is a "64 bit file"? A file is a sequence of goddam bytes.
See subject: Plus, save CPU/RAM/Other I-O by cutting off Server + Workstation services, remove NetBIOS over TCP/IP & Client for Microsoft Networks (& other CRAP there you don't need running when ALL YOU NEED is TCP/IP to be online) if all you have is a single machine @ home w/ no LAN? You're ALL SET vs. this puny BULLSHIT weak 'attack'...
APK
P.S.=> I've put this out in a security guide I wrote for single system users that even surprisingly got me paid circa 1997-2006 ala https://www.google.com/search?q=%22HOW+TO+SECURE+Windows+2000%2FXP%22&btnG=Search&hl=en&gbv=1/ which uses guidance from the highly esteemed CIS Tool (which took fixes to their ware from "yours truly" too, no less)... apk