You mean the source links that provided all the same information as was given in the article, and no further details on the infection methods either?Don’t you wish Ars provided source links that people can click on to answer questions like this?
If the framework isn't getting installed in the wild -- you did RTFA, right? -- how can anyone say how it infects systems? So no, there are no such hints.While interesting, this looks remarkably like a Navy advisory. "Stand by to stand by!"
It's great that the article delineates what it can do.
But are there any hints on HOW it infects systems? Knowing that can at least offer come measure of preparation for when it does go fully functional in the wild. An ounce of prevention, and all that...
Generally speaking, malware has two components. The first component is the compromise that gets the software in the door. That's what you're asking about. The second component is the payload - the software that actually infects the machine and does whatever nasty things the threat actor wants it to do.But are there any hints on HOW it infects systems?
Which is a good reminder that the biggest security vulnerability has always been the people using the system. Particularly the 'management' types who are arrogantly ignorant and easy marks for even the simplest of social-engineering attacks. Why go through all the trouble of finding a software- or hardware-level vulnerability, when you can just dupe the CEO into giving away their system access?Generally speaking, malware has two components. The first component is the compromise that gets the software in the door. That's what you're asking about. The second component is the payload - the software that actually infects the machine and does whatever nasty things the threat actor wants it to do.
The malware being discussed here is the payload. It's useless in itself without a way to get it onto the target host, and it won't have the compromise mechanism attached - that usually gets attached as part of the campaign to infect hosts, because compromises come and go as they're found and patched.
If this is targeting cloud applications using Linux, the only "user" perse is the applications running on the containers or hypervisors, which in turn get "used" by the developers and security people configuring them and deploying them. Maybe a Linux sysadmin if they're lazy enough to use the instance irresponsibly.Which is a good reminder that the biggest security vulnerability has always been the people using the system. Particularly the 'management' types who are arrogantly ignorant and easy marks for even the simplest of social-engineering attacks. Why go through all the trouble of finding a software- or hardware-level vulnerability, when you can just dupe the CEO into giving away their system access?
Any sysadmins care to chime in here??
Recon that provides “detailed system and environment profiling, user and group enumeration, process and service discovery, filesystem and mount mapping, and mapping of local network topology and interfaces.”
Did you drop that link to another site for a reason?
That reads more like a sell sheet
Yeah... that's a good reminder to remove all that debug logging
- Cloud-first tradecraft. In addition to cloud detection, these modules collect “vast amounts of information about the infected machine, enumerating its hypervisor and detecting whether it is running in a Docker container or a Kubernetes pod.
As a Linux fan, while I could have done without the "nyah"'s, your point on Linux also being able to get malware is well takenThe article says
Yeah... that's a good reminder to remove all that debug loggingI'veuh... my colleague... has running in far too many containers inprod, uh I mean, isolated test environments.
And, as usual, I'll happily say to anyone who's ever said, "Linux can't get viruses": nyah, nyah, nyah!
If this is targeting cloud applications using Linux, the only "user" perse is the applications running on the containers or hypervisors, which in turn get "used" by the developers and security people configuring them and deploying them. Maybe a Linux sysadmin if they're lazy enough to use the instance irresponsibly.
So in order to run in the operating system, they'd need an entry point in said software running on those containers or hypervisors for said cloud apps.
In my company, “management” ( CEO, VP, CFO, etc) have only user level access to company equipment or systems.Which is a good reminder that the biggest security vulnerability has always been the people using the system. Particularly the 'management' types who are arrogantly ignorant and easy marks for even the simplest of social-engineering attacks. Why go through all the trouble of finding a software- or hardware-level vulnerability, when you can just dupe the CEO into giving away their system access?
Any sysadmins care to chime in here??
Im not seeing any influx of fresh inexperienced users in Linux. Im seeing a waning interest in sysops and devops as Ai and more automated tech are filling more of those roles and the experienced admins are trying to hold onto their existing jobs.With the rise in popularity of Linux it starts to get close to the attention Windows is getting. So the light veil of "Linux doesn't get malware" is getting lifted. Linux is seeing an influx of fresh, inexperienced users. That's a fat target. The incentives from this segment just overdrives the development of such frameworks that will subsequently hit enterprise deployments to.
What exactly is "a series of clusters of Linux malware" in this context?Company researchers discovered it last month in a series of clusters of Linux malware available through VirusTotal.
Inexperienced in Linux. Also you not seeing it doesn't tell you it's not happening, just means you were just looking the other way. When Windows 10 reached end of mainstream support a good chunk of users started trying their luck and experimenting with Linux. There's a small movement now in that direction, and with Valve as a huge supporter, the gaming market is starting to see some signs of a shift.Im not seeing any influx of fresh inexperienced users in Linux. Im seeing a waning interest in sysops and devops as Ai and more automated tech are filling more of those roles and the experienced admins are trying to hold onto their existing jobs.
Many of the YouTube channels that I used to follow for sysop tips, etc are no longer making new content.
While this was my first answer too, we're also a more mature operation. For those smaller or startup companies, CEO's, CFO's, etc are often over provisioned because they were the ones that started the processes to begin with. As they mature, those permissions get peeled back and placed on responsible parties.In my company, “management” ( CEO, VP, CFO, etc) have only user level access to company equipment or systems.
So, 2 things. First, if it's not infecting things in the wild, how did it end up on VirusTotal? I very much doubt the developers would have uploaded it themselves, so it probably was uploaded by someone who got infected, suggesting it is being installed in the wild.If the framework isn't getting installed in the wild -- you did RTFA, right? -- how can anyone say how it infects systems? So no, there are no such hints.
which suggests the framework includes at least some mechanism for infecting non-infected systems (even if only from inside an already compromised network). I can't be the only one curious to know what that mechanism is.These modules can provide additional stealth and specific tools for reconnaissance, privilege escalation, and lateral movement inside a compromised network.
It will use whatever exploit plug-in is available. As far we know this malware doesn't rely on a specific attack vector. It looks like a Malware-as-service management with reconnaissance, attack, exploit, implementation and persistence framework.While interesting, this looks remarkably like a Navy advisory. "Stand by to stand by!"
It's great that the article delineates what it can do.
But are there any hints on HOW it infects systems? Knowing that can at least offer come measure of preparation for when it does go fully functional in the wild. An ounce of prevention, and all that...
Also for the moment, I think servers/companies are a more worthwhile target for the effort on Linux malware than the average home user for most attacks.Inexperienced in Linux. Also you not seeing it doesn't tell you it's not happening, just means you were just looking the other way. When Windows 10 reached end of mainstream support a good chunk of users started trying their luck and experimenting with Linux. There's a small movement now in that direction, and with Valve as a huge supporter, the gaming market is starting to see some signs of a shift.
So yes, people are starting to move to Linux for their day to day PC needs. Not a lot but enough to start painting a target. Attackers go after easy targets.
setenforce 1
I get what you are saying in terms of 'management' types, but that is an awful broad brush to be using to describe what you feel are the most at-risk employees in a company. As someone who is a manager (in IT) and works with a lot of managers (across IT and the business), they range the same gambit that all other employees and people run. We have really good managers at the middle and upper levels that I know would not fall for spear phishing attacks, and we have senior system admins that I am very sure would fall for the most obvious of phishing attempts. Just because you have had bad experiences with managers in the past, doesn't mean all are the same.Which is a good reminder that the biggest security vulnerability has always been the people using the system. Particularly the 'management' types who are arrogantly ignorant and easy marks for even the simplest of social-engineering attacks. Why go through all the trouble of finding a software- or hardware-level vulnerability, when you can just dupe the CEO into giving away their system access?
Any sysadmins care to chime in here??
Senior Systems Engineer here.Which is a good reminder that the biggest security vulnerability has always been the people using the system. Particularly the 'management' types who are arrogantly ignorant and easy marks for even the simplest of social-engineering attacks. Why go through all the trouble of finding a software- or hardware-level vulnerability, when you can just dupe the CEO into giving away their system access?
Any sysadmins care to chime in here??
Does anyone understand how this would have been contributed to Virus Total?
If it hasn’t been deployed yet then how would someone have binaries to contribute?
The only idea I can come up with is another hacker getting access to what the Chinese group was working on and sharing it to spoil their efforts proactively.
Or someone has someone else on the inside to do this.
if it's not infecting things in the wild, how did it end up on VirusTotal? I very much doubt the developers would have uploaded it themselves, so it probably was uploaded by someone who got infected, suggesting it is being installed in the wild.
Enterprise deployments are also far better secured. But it's the same for Windows. Windows Servers are way better hardened and secured than the average desktop. But the (hundreds of) millions of desktops of average Joes supercharged the hunt for exploits. That quantity has a quality in itself.Also for the moment, I think servers/companies are a more worthwhile target for the effort on Linux malware than the average home user for most attacks.
If market shares change, that will change. The malware people want the most bang for their buck on the time/effort though.
I think you misspelled "proper" as "typical". Typical is "whatever template the provider has", which may or may not be proper.The typical Linux cloud has an exposed reverse proxy, with the HTTP, application, and user stores and database behind additional firewalls.
Similar personal response in reading the linked article. Looked like an ad in many ways.That reads more like a sell sheet
What could go wrong...Im not seeing any influx of fresh inexperienced users in Linux. Im seeing a waning interest in sysops and devops as Ai and more automated tech are filling more of those roles and the experienced admins are trying to hold onto their existing jobs.
Many of the YouTube channels that I used to follow for sysop tips, etc are no longer making new content.
Which is generally good advice, right up until you have to install software that doesn't know or care about selinux, and the result is that you either setenforce 0, or you go through the fucking tedious process of reverse engineering the software to figure out exactly what selinux settings it needs in order to work correctly.Now if they have root already you are screwed but....
Code:setenforce 1
Don't make Dan Walsh cry!
https://stopdisablingselinux.com/
Lots of malware gets uploaded to VirusTotal by the creators, to test which engines detect their wares. As in, all the time. Frequently, the people announcing their discovery of new malware omit the detail that they only found it on VT and didn't find evidence of it spreading in the wild. That's why I asked and added that detail to my story.So, 2 things. First, if it's not infecting things in the wild, how did it end up on VirusTotal? I very much doubt the developers would have uploaded it themselves, so it probably was uploaded by someone who got infected, suggesting it is being installed in the wild.
Secondly, TFA says
which suggests the framework includes at least some mechanism for infecting non-infected systems (even if only from inside an already compromised network). I can't be the only one curious to know what that mechanism is.