full-disclosure - Re: Microsoft Update Loader msrtwd.exe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: uberguidoz at gmail.com (Über GuidoZ)
Subject: Re: Microsoft Update Loader msrtwd.exe

Easy sparky. Maybe it isn't his choice that he cannot release the EXE.
It's entirely possible, in fact, quite likely, that some "higher up"
who knows dick about IT and viruses got scared and said "This cannot
be shared with anyone! If it doesm you'll lose your job". Just because
they are worried about their image or that the file might contain
sensitive data.

I have run into this situation MANY times. There is usually little you
can do about it as an IT staff member or a consultant. So the next
best thing - ask a group of people that might have a clue what's going
on, WITHOUT needing to see or analyze said file.

Sheesh, give the guy a break. The only pollution I've noticed lately
is rude comments.

-- 
Peace. ~G

On Thu, 2 Sep 2004 20:30:53 +0200 (CEST), Feher Tamas
<etomcat@...email.hu> wrote:
> Hello,
> 
> >Recently discovered a trojan(? - possibly a virus) called
> >msrtwd.exe. It's listed in the Registry as "Microsoft Update
> >Loader" Does anyone know anything about this?
> >(Un)Fortunately, I am not allowed to distribue the exe.
> 
> When the f*ck will people finally realize that it is NOT possible to say
> anything about a file without actually having the file?
> 
> If you wanna know what the f*ck this or that file is, go to and feed that
> file here:
> http://www.kaspersky.com/scanforvirus
> 
> Less than 50 chars to remember and you can stop polluting this list.
> Wow!
> 
> Regards: Tamas Feher.