Jump to content
  • Welcome!

    Register and log in easily with Twitter or Google accounts!

    Or simply create a new Huddle account. 

    Members receive fewer ads , access our dark theme, and the ability to join the discussion!

     

Computer help! Fugging rootkits!


southcakalac

Recommended Posts

Malwarebyte's has detected a rootkit on my computer. I carries a name of .TDSS. Malwarebytes says it removes it but then when I check again it there again. I read some stuff on the web about removing them and it seems complicated.

Any computer guys here that can lend a hand?:confused:

Edit: I'm running windows vista.

Link to comment
Share on other sites

I've never run into this particular dilemma, but in all the other infections I've had on my PC, I generally run two or three different spyware/AV programs to make sure it's gone. Malwarebytes is pretty good though... maybe boot to safe mode and run it again?

Maybe someone else has specific experience with this one on here...

Link to comment
Share on other sites

I've had this problem before, the only way get rid of it for good is to remove it from the registry and malwarebytes won't do that. You need to type regedit into the search/command line that opens up after you hit the start button. You want to look for a registry entry under HKEY_LOCAL_MACHINE>SOFTWARE that looks like gibberish. It will usually be a bunch of random letters together. Double check that its nothing important and then blast it/delete it. After that is done you'll have rendered the rootkit useless after you re-boot as it won't be able to run anymore. From there you should be able to remove it for good after doing another malwarebytes scan.

Your rootkit must not be too bad as the one I had wouldn't even allow malwarebytes to do a scan. I had to find this tool that found hidden registry entries to get rid of the sucker.

Link to comment
Share on other sites

Format C:

I've had this problem before, the only way get rid of it for good is to remove it from the registry and malwarebytes won't do that. You need to type regedit into the search/command line that opens up after you hit the start button. You want to look for a registry entry under HKEY_LOCAL_MACHINE>SOFTWARE that looks like gibberish. It will usually be a bunch of random letters together. Double check that its nothing important and then blast it/delete it. After that is done you'll have rendered the rootkit useless after you re-boot as it won't be able to run anymore. From there you should be able to remove it for good after doing another malwarebytes scan.

Your rootkit must not be too bad as the one I had wouldn't even allow malwarebytes to do a scan. I had to find this tool that found hidden registry entries to get rid of the sucker.

Screwing around in the registry when you aren't 100% sure what you're looking for can end badly.

Link to comment
Share on other sites

I had a similar problem with my laptop....I tried everything and I personally agree messing with ure registry can have serious consequences...I recommend saving ure pics, and important files and rebooting the thing.

Depending on how bad the rootkit is, he may not be able to do that. Personally mine locked down any non-read activity to all of my drives thus elminating my ability to copy off important stuff and blast the thing. Honestly, its not that hard to do what I said. My bogus entry looked like this:

gxbhnxd

Now does the above resemble anything close to something "critical" that would crash your PC? As long as he doesn't mess with windows registry entrys (which wouldn't be found under the HKEY_LOCAL_MACHINE>SOFTWARE section) then the worst that could happen is a given program (whatever is erroneously deleted) would need to be reinstalled to work effectively again.

Link to comment
Share on other sites

Malwarebytes' Anti-Malware 1.41

Database version: 2775

Windows 6.0.6001 Service Pack 1

9/10/2009 4:52:05 PM

mbam-log-2009-09-10 (16-52-05).txt

Scan type: Quick Scan

Objects scanned: 85265

Time elapsed: 6 minute(s), 55 second(s)

Memory Processes Infected: 0

Memory Modules Infected: 0

Registry Keys Infected: 1

Registry Values Infected: 0

Registry Data Items Infected: 0

Folders Infected: 0

Files Infected: 0

Memory Processes Infected:

(No malicious items detected)

Memory Modules Infected:

(No malicious items detected)

Registry Keys Infected:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbiwkmeatecqxs (Rootkit.TDSS) -> Quarantined and deleted successfully.

Registry Values Infected:

(No malicious items detected)

Registry Data Items Infected:

(No malicious items detected)

Folders Infected:

(No malicious items detected)

Files Infected:

(No malicious items detected)

This is what is says. I've looked through the registry and can't seem to locate it. I'm worried about deleting the wrong thing. I will keep trying though.

Link to comment
Share on other sites

Do just a standard search on your computer for all files containing the file name part "kbiwkm". What comes up?

Yes if you want to be super safe, you can do a search for that filename in the registry, re-name the file slightly once you find it, and then re-boot. The registry entry should show up after that. Also make sure that you have the folder options setup on your C:\ drive so that you can see hidden files and windows critical system files. These rootkits will hide themselves by disguising themselves to fall under those umbrellas and you'll never catch them with a search unless you check those boxes under folder options first.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


  • PMH4OWPW7JD2TDGWZKTOYL2T3E.jpg

  • Topics

  • Posts

    • Looks like Troy Hill was ready to hold his team accountable and a certain DC thought it would make the defense worse. I'm sure Troy Hill was the problem with the defense. Watch him go back to Brandon Staley with the 49ers now.
    • Some here have it wrong when based on hard numbers that determine a game. Here's a lengthy and deep analysis. Don't continue reading if you are not willing to look at the good and bad of your favorite players. The pass blocking was horrendous in the first half, and Dalton still kept the game competitive. Dalton was obviously directed to throw it to Thomas. Thomas ran his route horribly and didn't come back to the ball. The DB had an easy path to just race in front of Thomas. He's a TE who should be using his body to keep a DB from doing that. Lazy play by Thomas. The throw was good and it was the correct read (delivered 15 yards downfield with 3 to 5 yards to the sideline is where that ball was placed for Thomas). Here's how the drives went for the Falcons game. Drive 1: Ekwonu killed it. Drive 2: Heavy Dalton passing (Johnson & Moore). TD Drive 3: Dalton short passing (J.Sanders & XL). Punt Drive 4: Heavy Hubbard touches. FG Drive 5: Hubbard/M.Sanders touches. Punt (Running game failed and forced Dalton into 2 long passing downs. Got a PI to keep drive alive on one.) Drive 6: Heavy Dalton passing (5 targeted receivers). TD Drive 7: Running & short passing game to open the 2nd half. FG (Hubbard, Mingo, M.Sanders, J.Sanders, Thomas) OL ended the drive with a 2nd and 19. This is the ONLY drive the Panthers had for 3Q. Defensive failure Drive 8: Heavy Hubbard touches with TE targets. INT (Ian Thomas gave up INT with a lazy route and zero awareness of using his body to keep the DB from easily crossing his body. The play was called for Thomas and the play worked perfectly with him cutting through the zone to a wide open pocket. All Thomas had to do was get his body in between the trailing defender and the ball while staying on a line to the sideline. Thomas rounded his break and drifted to 18 yards deep at the end of his route. Gave the advantage to the speed of the trail defender. Pass was on point for a 15 yard crossing route. Play call was good. Receiver execution of a dig route was awful). The defense and Thomas in the 2nd half ended the game. Scoring % is 50% after this INT. That's still good for an offense. [Down 15 points with 5 minutes left. Running game has produced 6 points in 5 of 8 drives lasting 3 to 5 minutes per drive. Dalton has been successful on 2 of the 3 drives he was called on with the 1 failed drive stopped with bad pass blocking and relying on a TE.] Drive 9: All pass with defense protecting a lead. OL pass blocking fails again putting Dalton into a 2nd and 20. Dalton gets it to a 4th & 4 and throws incomplete with Ekwonu (one on one) thrown into him in 2 seconds forcing a high throw. (Canales, Dalton and Johnson were on point for a likely 1st down. Ekwonu pass blocking failed.) Turnover on downs. Drive 10: 2 minutes to go down 18 points. All pass. INT (Dalton didn't anticipate the CB jumping the route after reading a deep zone) The defense only stopped 2 drives from scoring. The OL lacks discipline and is a liability with their pass blocking. No one can excuse Ekwonu for what he does in pass blocking. It continues to cost the Panthers late in games, and on critical 4th down pass plays. The OL is very good at run blocking, but the RBs are not as good as fans want to believe. They are not playmakers to open up a game with a strong run blocking OL. The RBs are only good enough for controlling clock with a lead (and that needs to be more consistent). Too many missed opportunities from the RBs behind this OL. The TEs and Mingo are liabilities in the passing game. Their mistakes plus the lack of discipline on the OL is leading to way too many 3rd & longs. 7 of 12 3rd downs were long. 4 of the 7 were 3rd & 10+. The most efficient part of the team against the Falcons was Dalton, Johnson, Coker and Canales' play calling. XL is close to being in this group. Negative plays that resulted in 3rd & longs, failed 4th downs, INTs, and fumbles lost : Hubbard 3; Ekwonu 4; Thomas 2; J.Sanders 1; M.Sanders 1; Lewis 1; Nijman 1; Dalton 1. 1st downs/TDs converted: Rushing: Hubbard 6; M.Sanders 1; Dalton 1. Passing: Dalton 13 (Johnson 6; M.Sanders 1; Coker 2; J.Sanders 1; Legette 2; Hubbard 1). Top 3 liabilities: 1. Ekwonu 2. Hubbard 3. Thomas. Top 3 strengths: 1. Dalton 2. Hubbard 3. Johnson Anyone with a 1 doesn’t make a list. The goal is to have ZERO players on the liability list and 3 or more players on the strengths list. Then you want the opposite for the opponent to gauge the defense. Only 1 player of the Falcons made the liability list (Algiers with back to back runs for 0 yards on the 10th drive (final) of the game). Not a single Falcons OL with more than 1 critical mistake. Falcons only had 2 legit 3rd and longs all game (4 if you add the final plays of the game for them with the kneel downs). The Falcons converted 25 times in 9 drives. That makes them look better than the 5-0 Chiefs offense. Panthers' conversions by week: 1. 11; 2. 7; 3. 24; 4. 24; 5. 14; 6. 21. Dalton has been the key factor in the offense consistently converting 20+. The Bears game was planned around Hubbard carrying it to keep the Panthers defense off the field, and that failed. That is the only game Dalton has started that there hasn't been a single drive over 4 minutes in the 1st half (Dalton targeted 2 WRs on 2 passes until the 2 minute warning against the Bears). Realize the pass blocking OL and their discipline is a liability. The RBs lack of consistency is a liability. The TEs are a huge problem. The Panthers need a 3rd down back desperately, and Mingo should be converted to that role for now. The run blocking OL is carrying average RBs. Dalton is good enough to win and has done well playing through poor pass blocking. The receivers outside of Mingo are executing well. Canales is getting receivers open and calling plays to beat the defense. That's the state of the offense. Good enough to win, but not on at a level to put up 40 points per game. The offense has to worry about keeping up with their defense rather than simply executing to be good and win games at the end. List Dalton's critical mistakes that have ended a drive. Ekwonu, Mingo & Thomas are responsible for 3 of his 4 interceptions. His 3rd or 4th and short passes have failed how many times without being impacted by a terrible block or dropped pass?  45 drives to look at. I've already told you 3 that are not on Dalton. 10 resulted in TDs & 3 were end of game/half. That leaves 29 drives. Go see how they ended, and who's responsible. I already know, and I don't think some of you are willing to acknowledge who the drive killers are on the offense. It's not Dalton leading the way. Tough truths.
    • Haven't had time to pay attention to college ball the last couple weeks but seems like all the mock drafts have Sanders, Hunter, and Ward in the top 5 and then kinda mixed bag after that. I like that Ward is a playmaker with a little Favre style in him, seems real comfortable leading the huddle. Very different vibe from the soft stuff we've dealt with the last couple years. I believe he would no doubt beat out BY in a camp battle for what it's worth
×
×
  • Create New...