Can I remove “Linux/Ebury Operation Windigo” without wiping the entire drive?
I used chkrootkit
, which told me that I had "Linux/Ebury Operation Windigo" installed, I doubled checked by running ssh -G
which printed out usage, without "illegal option". I removed all ssh files and reinstalled it, but when I ran ssh -G
again I still had it, also detected by chkrootkit
.
Can you remove this without wiping the entire drive? Are there any files I should be looking for?
osx malware chkrootkit
add a comment |
I used chkrootkit
, which told me that I had "Linux/Ebury Operation Windigo" installed, I doubled checked by running ssh -G
which printed out usage, without "illegal option". I removed all ssh files and reinstalled it, but when I ran ssh -G
again I still had it, also detected by chkrootkit
.
Can you remove this without wiping the entire drive? Are there any files I should be looking for?
osx malware chkrootkit
add a comment |
I used chkrootkit
, which told me that I had "Linux/Ebury Operation Windigo" installed, I doubled checked by running ssh -G
which printed out usage, without "illegal option". I removed all ssh files and reinstalled it, but when I ran ssh -G
again I still had it, also detected by chkrootkit
.
Can you remove this without wiping the entire drive? Are there any files I should be looking for?
osx malware chkrootkit
I used chkrootkit
, which told me that I had "Linux/Ebury Operation Windigo" installed, I doubled checked by running ssh -G
which printed out usage, without "illegal option". I removed all ssh files and reinstalled it, but when I ran ssh -G
again I still had it, also detected by chkrootkit
.
Can you remove this without wiping the entire drive? Are there any files I should be looking for?
osx malware chkrootkit
osx malware chkrootkit
asked Mar 7 '16 at 22:07
DisplayName
4,39394479
4,39394479
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
There are more than one way to find out if you are actually infected. From what I have read, these two are the tried and true methods as chkrootkit only returns suspicion about being infected, not a guarantee. If you run the following two commands and nothing comes back, I would say it's a false positive.
This one searches for it's network socket
netstat -nap | grep "@/proc/udevd"
This one searches for the module it installs
find /lib* -type f -name libns2.so
add a comment |
(I know this is an old thread, but I'm adding additional information for clarity.)
If you are actually infected, pretty much the only reliable solution is to wipe and reinstall. However, it is well established that as of the moment, chrootkit frequently identifies a false positive for Windigo.
In the whitepaper on Windigo that ESET published, it details another method of checking for windigo by looking at shared memory segments.
https://www.welivesecurity.com/wp-content/uploads/2014/03/operation_windigo.pdf
Essentially, you need to run:
sudo ipcs -m
and look for any entries that have permissions greater than 600 or that use a relatively large amount of memory. If there aren't any, then you are likely clean.
If there are, then note the segment id ( shmid ) and run:
sudo ipcs -m -p
get the process id ( pid ) and you can find out what the process is with:
sudo ps aux | grep <pid>
If you don't recognize the process then do some additional research on it to determine whether it is a potential threat. There is a good technical analysis including SHA-1 hashes of the infection at https://www.welivesecurity.com/2014/02/21/an-in-depth-analysis-of-linuxebury/ that will be helpful.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f268271%2fcan-i-remove-linux-ebury-operation-windigo-without-wiping-the-entire-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There are more than one way to find out if you are actually infected. From what I have read, these two are the tried and true methods as chkrootkit only returns suspicion about being infected, not a guarantee. If you run the following two commands and nothing comes back, I would say it's a false positive.
This one searches for it's network socket
netstat -nap | grep "@/proc/udevd"
This one searches for the module it installs
find /lib* -type f -name libns2.so
add a comment |
There are more than one way to find out if you are actually infected. From what I have read, these two are the tried and true methods as chkrootkit only returns suspicion about being infected, not a guarantee. If you run the following two commands and nothing comes back, I would say it's a false positive.
This one searches for it's network socket
netstat -nap | grep "@/proc/udevd"
This one searches for the module it installs
find /lib* -type f -name libns2.so
add a comment |
There are more than one way to find out if you are actually infected. From what I have read, these two are the tried and true methods as chkrootkit only returns suspicion about being infected, not a guarantee. If you run the following two commands and nothing comes back, I would say it's a false positive.
This one searches for it's network socket
netstat -nap | grep "@/proc/udevd"
This one searches for the module it installs
find /lib* -type f -name libns2.so
There are more than one way to find out if you are actually infected. From what I have read, these two are the tried and true methods as chkrootkit only returns suspicion about being infected, not a guarantee. If you run the following two commands and nothing comes back, I would say it's a false positive.
This one searches for it's network socket
netstat -nap | grep "@/proc/udevd"
This one searches for the module it installs
find /lib* -type f -name libns2.so
answered Jul 21 '16 at 8:22
deadbabykitten
112
112
add a comment |
add a comment |
(I know this is an old thread, but I'm adding additional information for clarity.)
If you are actually infected, pretty much the only reliable solution is to wipe and reinstall. However, it is well established that as of the moment, chrootkit frequently identifies a false positive for Windigo.
In the whitepaper on Windigo that ESET published, it details another method of checking for windigo by looking at shared memory segments.
https://www.welivesecurity.com/wp-content/uploads/2014/03/operation_windigo.pdf
Essentially, you need to run:
sudo ipcs -m
and look for any entries that have permissions greater than 600 or that use a relatively large amount of memory. If there aren't any, then you are likely clean.
If there are, then note the segment id ( shmid ) and run:
sudo ipcs -m -p
get the process id ( pid ) and you can find out what the process is with:
sudo ps aux | grep <pid>
If you don't recognize the process then do some additional research on it to determine whether it is a potential threat. There is a good technical analysis including SHA-1 hashes of the infection at https://www.welivesecurity.com/2014/02/21/an-in-depth-analysis-of-linuxebury/ that will be helpful.
add a comment |
(I know this is an old thread, but I'm adding additional information for clarity.)
If you are actually infected, pretty much the only reliable solution is to wipe and reinstall. However, it is well established that as of the moment, chrootkit frequently identifies a false positive for Windigo.
In the whitepaper on Windigo that ESET published, it details another method of checking for windigo by looking at shared memory segments.
https://www.welivesecurity.com/wp-content/uploads/2014/03/operation_windigo.pdf
Essentially, you need to run:
sudo ipcs -m
and look for any entries that have permissions greater than 600 or that use a relatively large amount of memory. If there aren't any, then you are likely clean.
If there are, then note the segment id ( shmid ) and run:
sudo ipcs -m -p
get the process id ( pid ) and you can find out what the process is with:
sudo ps aux | grep <pid>
If you don't recognize the process then do some additional research on it to determine whether it is a potential threat. There is a good technical analysis including SHA-1 hashes of the infection at https://www.welivesecurity.com/2014/02/21/an-in-depth-analysis-of-linuxebury/ that will be helpful.
add a comment |
(I know this is an old thread, but I'm adding additional information for clarity.)
If you are actually infected, pretty much the only reliable solution is to wipe and reinstall. However, it is well established that as of the moment, chrootkit frequently identifies a false positive for Windigo.
In the whitepaper on Windigo that ESET published, it details another method of checking for windigo by looking at shared memory segments.
https://www.welivesecurity.com/wp-content/uploads/2014/03/operation_windigo.pdf
Essentially, you need to run:
sudo ipcs -m
and look for any entries that have permissions greater than 600 or that use a relatively large amount of memory. If there aren't any, then you are likely clean.
If there are, then note the segment id ( shmid ) and run:
sudo ipcs -m -p
get the process id ( pid ) and you can find out what the process is with:
sudo ps aux | grep <pid>
If you don't recognize the process then do some additional research on it to determine whether it is a potential threat. There is a good technical analysis including SHA-1 hashes of the infection at https://www.welivesecurity.com/2014/02/21/an-in-depth-analysis-of-linuxebury/ that will be helpful.
(I know this is an old thread, but I'm adding additional information for clarity.)
If you are actually infected, pretty much the only reliable solution is to wipe and reinstall. However, it is well established that as of the moment, chrootkit frequently identifies a false positive for Windigo.
In the whitepaper on Windigo that ESET published, it details another method of checking for windigo by looking at shared memory segments.
https://www.welivesecurity.com/wp-content/uploads/2014/03/operation_windigo.pdf
Essentially, you need to run:
sudo ipcs -m
and look for any entries that have permissions greater than 600 or that use a relatively large amount of memory. If there aren't any, then you are likely clean.
If there are, then note the segment id ( shmid ) and run:
sudo ipcs -m -p
get the process id ( pid ) and you can find out what the process is with:
sudo ps aux | grep <pid>
If you don't recognize the process then do some additional research on it to determine whether it is a potential threat. There is a good technical analysis including SHA-1 hashes of the infection at https://www.welivesecurity.com/2014/02/21/an-in-depth-analysis-of-linuxebury/ that will be helpful.
answered Dec 16 at 19:22
SolStack
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f268271%2fcan-i-remove-linux-ebury-operation-windigo-without-wiping-the-entire-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown