chevron_left chevron_right
Login Register invert_colors photo_library


Stay updated and chat with others! - Join the Discord!
Thread Rating:
  • 0 Vote(s) - 0 Average


how we Know if any Keylogger run in our Computer filter_list
Author
Message
how we Know if any Keylogger run in our Computer #1
i heard about some way with "run" or "CMD" that we can know if any key logger run in our computer.., can u tell me if u know that ???
or any other methods ??? :innocent:
[Image: Wfxdx.png]

Reply

RE: how we Know if any Keylogger run in our Computer #2
I think what you are looking for is:
Code:
netstat -b

Description:
Quote:Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in [] at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
permissions.

You will get an output like this:
Code:
Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:49160        PC:49161               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49161        PC:49160               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49162        PC:49163               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49163        PC:49162               ESTABLISHED
[firefox.exe]
  TCP    192.168.1.2:49165      67.221.174.64:https    ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49185      hx-in-f125:5222        ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49190      baymsg1030127:msnp     ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49192      jabber-01-01-snc2:5222  ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49287      download:http          CLOSE_WAIT
[cmdagent.exe]
  TCP    192.168.1.2:49288      vip1:http              CLOSE_WAIT
[cmdagent.exe]
  TCP    192.168.1.2:49341      by2msg4010804:msnp     ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49349      httpcs204:http         ESTABLISHED
[digsby-app.exe]
[Image: rytwG00.png]
Redcat Revolution!

Reply

RE: how we Know if any Keylogger run in our Computer #3
(06-30-2011, 07:51 AM)Coder-san Wrote: I think what you are looking for is:
Code:
netstat -b

Description:
Quote:Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in [] at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
permissions.

You will get an output like this:
Code:
Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:49160        PC:49161               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49161        PC:49160               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49162        PC:49163               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49163        PC:49162               ESTABLISHED
[firefox.exe]
  TCP    192.168.1.2:49165      67.221.174.64:https    ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49185      hx-in-f125:5222        ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49190      baymsg1030127:msnp     ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49192      jabber-01-01-snc2:5222  ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49287      download:http          CLOSE_WAIT
[cmdagent.exe]
  TCP    192.168.1.2:49288      vip1:http              CLOSE_WAIT
[cmdagent.exe]
  TCP    192.168.1.2:49341      by2msg4010804:msnp     ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49349      httpcs204:http         ESTABLISHED
[digsby-app.exe]

thanks Admin Smile think this is i searched about ,but if you can you explain me more ., how to check it ??
Edit - netstat -b is not workin for me why is that ?? :o but netstat -a is working ???
[Image: Wfxdx.png]

Reply

RE: how we Know if any Keylogger run in our Computer #4
I'm not sure what can be the problem. Here is the full contents of netstat:

Quote:Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

E:\Users\User>netstat /?

Displays protocol statistics and current TCP/IP network connections.

NETSTAT [-a] [-b] [-e] [-f] [-n] [-o] [-p proto] [-r] [-s] [-t] [interval]

-a Displays all connections and listening ports.
-b Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in [] at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
permissions.
-e Displays Ethernet statistics. This may be combined with the -s
option.
-f Displays Fully Qualified Domain Names (FQDN) for foreign
addresses.
-n Displays addresses and port numbers in numerical form.
-o Displays the owning process ID associated with each connection.
-p proto Shows connections for the protocol specified by proto; proto
may be any of: TCP, UDP, TCPv6, or UDPv6. If used with the -s
option to display per-protocol statistics, proto may be any of:
IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, or UDPv6.
-r Displays the routing table.
-s Displays per-protocol statistics. By default, statistics are
shown for IP, IPv6, ICMP, ICMPv6, TCP, TCPv6, UDP, and UDPv6;
the -p option may be used to specify a subset of the default.
-t Displays the current connection offload state.
interval Redisplays selected statistics, pausing interval seconds
between each display. Press CTRL+C to stop redisplaying
statistics. If omitted, netstat will print the current
configuration information once.


E:\Users\User>
[Image: rytwG00.png]
Redcat Revolution!

Reply

RE: how we Know if any Keylogger run in our Computer #5
hmm.., i'm using Dongle right now, maybe problem is that.., Smile Smile Smile thanks Coder-san
[Image: Wfxdx.png]

Reply

RE: how we Know if any Keylogger run in our Computer #6
HI
IS ANY ONE KNOW THAT HOW TO SET KEEP ASKING PASSWORD IN OUTLOOK EXPRESS BY BATCH FILE.........
[Image: jcS43.png]

Reply

RE: how we Know if any Keylogger run in our Computer #7
(06-30-2011, 08:01 AM)Shining White Holmse Wrote:
(06-30-2011, 07:51 AM)Coder-san Wrote: I think what you are looking for is:
Code:
netstat -b

Description:
Quote:Displays the executable involved in creating each connection or
listening port. In some cases well-known executables host
multiple independent components, and in these cases the
sequence of components involved in creating the connection
or listening port is displayed. In this case the executable
name is in [] at the bottom, on top is the component it called,
and so forth until TCP/IP was reached. Note that this option
can be time-consuming and will fail unless you have sufficient
permissions.

You will get an output like this:
Code:
Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    127.0.0.1:49160        PC:49161               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49161        PC:49160               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49162        PC:49163               ESTABLISHED
[firefox.exe]
  TCP    127.0.0.1:49163        PC:49162               ESTABLISHED
[firefox.exe]
  TCP    192.168.1.2:49165      67.221.174.64:https    ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49185      hx-in-f125:5222        ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49190      baymsg1030127:msnp     ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49192      jabber-01-01-snc2:5222  ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49287      download:http          CLOSE_WAIT
[cmdagent.exe]
  TCP    192.168.1.2:49288      vip1:http              CLOSE_WAIT
[cmdagent.exe]
  TCP    192.168.1.2:49341      by2msg4010804:msnp     ESTABLISHED
[digsby-app.exe]
  TCP    192.168.1.2:49349      httpcs204:http         ESTABLISHED
[digsby-app.exe]

thanks Admin Smile think this is i searched about ,but if you can you explain me more ., how to check it ??
Edit - netstat -b is not workin for me why is that ?? :o but netstat -a is working ???

You probably forgot to run cmd.exe as administrator.

[Image: cmdrunadmin.jpg]
I'm Back!(05-16-12) (I miss Sage)

[link=http://goo.gl/NMwwO]Live Hacking CD[/link]

[link=http://goo.gl/ab9Ec]How to: Hack Windows Admin Password[/link]


Reply

RE: how we Know if any Keylogger run in our Computer #8
Yeah man....... <3 Thanks.. » ¥ « Smile
[Image: Wfxdx.png]

Reply

RE: how we Know if any Keylogger run in our Computer #9
The easiest way is to install antivirus in your compter, most of the antivirus will pick up keylogger software, however, if the keylogger is added to the ignore list, it's hard to find out it.
Present is the best present for me.
remote monitoring software
remote spy software
SMS spy

Reply

RE: how we Know if any Keylogger run in our Computer #10
Try MBAM or SpyBot Destroy.
Spoiler:
[Image: unledbyds.png]

Reply






Users browsing this thread: 1 Guest(s)