SoylentNews is people
SoylentNews
WikiLeaks has today published the 15th batch of its ongoing Vault 7 leak, this time detailing two alleged CIA implants that allowed the agency to intercept and exfiltrate SSH (Secure Shell) credentials from targeted Windows and Linux operating systems using different attack vectors.
Secure Shell or SSH is a cryptographic network protocol used for remote login to machines and servers securely over an unsecured network.
Dubbed BothanSpy — implant for Microsoft Windows Xshell client, and Gyrfalcon — targets the OpenSSH client on various distributions of Linux OS, including CentOS, Debian, RHEL (Red Hat), openSUSE and Ubuntu.
Both implants steal user credentials for all active SSH sessions and then sends them to a CIA-controlled server.
BothanSpy is installed as a Shellterm 3.x extension on the target machine and only works if Xshell is running on it with active sessions.
[...] Gyrfalcon targets Linux systems (32 or 64-bit kernel) using a CIA-developed JQC/KitV rootkit for persistent access.
Source: The Hacker News
The latest addition to WikiLeaks' Vault 7 cache of CIA tools and documents gives details of tools used by the agency to attack Windows and Linux computers. The BothanSpy and Gyrfalcon projects can be used to intercept and exfiltrate SSH (Secure Shell) credentials.
BothanSpy is used to target Windows, while Gyrfalcon is used for Linux machines, with both working in different ways. A number of popular distros can be hit by Gyrfalcon, including CentOS, Debian, RedHat, openSUSE and Ubuntu, and both tools function as implants that steal credentials before transmitting them to a CIA server.
The leaked documentation for the tools was updated as recently as March 2015, and the file relating to BothanSpy reveals that XShell needs to be installed as it itself installs as a Shellterm extension. There are smatterings of humor throughout the file, with a warning that: "It does not destroy the Death Star, nor does it detect traps laid by The Emperor to destroy Rebel fleets." There is also the introductory quip: "Many Bothan spies will die to bring you this information, remember their sacrifice."
Source: BetaNews
(Score: 2) by kaszz on Saturday July 08 2017, @11:37AM (3 children)
It seems to be affected the machine already must have been compromised with some rootkit. Thus keep a lookout for modified system files, loadable kernel modules, what processes that are loaded and firewalls:
The rest of the tools seems to 90% be about the Microsoft shit and some IoT that let their microphones and cameras do all kinds of surveillance for free. Thus it might be an idea to really tighten your firewall, both ways. And actively destroy any WiFi traffic.
This also makes it obvious that binary blobs is a gigantic security vulnerability and that being able to run free open source software on bought hardware should be a requirement when that is possible. This means BIOS, Intel AMT, harddisc firmware, Network interface firmware, Raspberry-Pi graphics blob, NVidia free but binary only driver, network equipment etc. Be aware of processes or modules residing in memory that lack a corresponding binary. In memory only executable are used to cover tracks so at least a minimum reboot can flush them.
Be observant on how careful your peers are with sensitive information. If they blabber about it on facebook, twitter or any other junk service, then stop divulging anything to them. The same goes if they use insecure devices to communicate your personal information on Microsoft Windows 10 or computerphones (smartphones).
It might be useful to account detailed usage of energy, network, radio spectrum etc to spot electronic intrusions.
(Score: 3, Funny) by c0lo on Saturday July 08 2017, @11:55AM
Eh, you can skip the all the above by simply relocation to Las Vegas: what happens there, stays there, guaranteed no ex-filtration.
(grin)
https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
(Score: 2) by frojack on Saturday July 08 2017, @04:55PM (1 child)
Exactly. Once you have that, you could just as well email the private keys and be done with it.
I suppose the real target here is the recording of live ssh sessions, but that seems once you have your root kit in place you wouldn't need any ssh keys anymore because its easier to grab the data after it has been decrypted.
No, you are mistaken. I've always had this sig.
(Score: 2) by kaszz on Saturday July 08 2017, @05:24PM
Rather by extracting the keys the traffic can be tapped and decoded from the network backbone, just like "Room 641A" in San Francisco hints. That way no extra ex-filtration traffic is required and all recording can be done in silence.