elhacker.net cabecera Bienvenido(a), Visitante. Por favor Ingresar o Registrarse
¿Perdiste tu email de activación?.

 

 


Tema destacado: Guía actualizada para evitar que un ransomware ataque tu empresa


+  Foro de elhacker.net
|-+  Foros Generales
| |-+  Dudas Generales (Moderador: engel lex)
| | |-+  que puedo hacer teniendo la MAC de un atacante?
0 Usuarios y 1 Visitante están viendo este tema.
Páginas: [1] 2 Ir Abajo Respuesta Imprimir
Autor Tema: que puedo hacer teniendo la MAC de un atacante?  (Leído 6,856 veces)
Hason


Desconectado Desconectado

Mensajes: 787


Keep calm and use the spiritual force


Ver Perfil WWW
que puedo hacer teniendo la MAC de un atacante?
« en: 12 Agosto 2015, 13:55 pm »

Pues , es que tengo alguna mac que he pillado scaneando con ettercap y wireshark, pero no se que puedo hacer con la mac.
Alguna pista o algo de que se podría hacer, he buscado información pero no se que hacer.
Algún programa o algo.

De todas formas, supongo, que probablemente haya cambiado la mac con el macchanger por ejemplo, y no sea la mac real.... que podría hacer.

Entiendo que no querais decirmelo, pero por lo menos podías encaminarme un poco.

Un saludo.


En línea

Verse constantemente expuesto al peligro puede generar desprecio hacia él.
El que resiste, gana
Aníbal sabía como conseguir la victoria, pero no cómo utilizarla
"Houston, tenemos un problema": los detalles y curiosidades tras uno de los mensajes de alarma más famosos de la historia
https://amaltea.wordpress.com/2008/03/06/proverbios-y-refranes-grecolatinos/
engel lex
Moderador Global
***
Desconectado Desconectado

Mensajes: 15.514



Ver Perfil
Re: que puedo hacer teniendo la MAC de un atacante?
« Respuesta #1 en: 12 Agosto 2015, 14:08 pm »

el atacante estaba fisicamente a alcance de tu wifi?


En línea

El problema con la sociedad actualmente radica en que todos creen que tienen el derecho de tener una opinión, y que esa opinión sea validada por todos, cuando lo correcto es que todos tengan derecho a una opinión, siempre y cuando esa opinión pueda ser ignorada, cuestionada, e incluso ser sujeta a burla, particularmente cuando no tiene sentido alguno.
Randomize
Colaborador
***
Desconectado Desconectado

Mensajes: 20.599


Beautiful Day


Ver Perfil
Re: que puedo hacer teniendo la MAC de un atacante?
« Respuesta #2 en: 12 Agosto 2015, 14:56 pm »

Ettercap...

Wireshark...


Puede estar en las antípodas de ande estés, ya sabes, otro país, otra jurisdición, otras normas...
En línea

Hason


Desconectado Desconectado

Mensajes: 787


Keep calm and use the spiritual force


Ver Perfil WWW
Re: que puedo hacer teniendo la MAC de un atacante?
« Respuesta #3 en: 12 Agosto 2015, 15:07 pm »

El atacante está en mi red, está fijo, estoy pillando varias macs, con el navegador desconectado y sin actualizar nada.
Estoy escaneando su host , que es 0.0.0.0 , con mi router , y me aparecen diversas macs que no son las mias, creo que también aparecen direcciones ip.
Con el wireshark me dice que sufro arp spoofing, y que tengo la mac duplicada.

Haber, no es que se me conecte por wifi, lo tengo cerrado, se conecta contiunamente por que esta en  mi pc, en el chipset del controlador de red , si no me equivoco.

Entonces siempre está conectado, las capturas siempre me dan macs y direcciones, aclaro, con ettercap, y con wireshark.


El que me lo hace utiliza proxys claro, pero algo se podrá hacer o no?? aparte de ir a las autoridades, que aquí donde vivo, me hace falta un experto para que me avale.

Estoy intentando subir las tomas de pantalla, pero no me funciona creo, las intentó postear,pero en previsualizar mensaje, no me aparecen... no se por que no puedo subir las imágenes, y no puedo copiar y pegar desde wireshark....






En línea

Verse constantemente expuesto al peligro puede generar desprecio hacia él.
El que resiste, gana
Aníbal sabía como conseguir la victoria, pero no cómo utilizarla
"Houston, tenemos un problema": los detalles y curiosidades tras uno de los mensajes de alarma más famosos de la historia
https://amaltea.wordpress.com/2008/03/06/proverbios-y-refranes-grecolatinos/
Hason


Desconectado Desconectado

Mensajes: 787


Keep calm and use the spiritual force


Ver Perfil WWW
Re: que puedo hacer teniendo la MAC de un atacante?
« Respuesta #4 en: 12 Agosto 2015, 15:08 pm »

Pues , no se han posteado las imagenes, y lo hago bien creo, estoy dandole al icono de insertar imagen , y pongo la imagen .png, pero no se postean.
En cambio cuando pongo un enlace de youtube, si que puedo, pero no puedo poner las pruebas que confirman lo que digo. :-[

Un saludo.
En línea

Verse constantemente expuesto al peligro puede generar desprecio hacia él.
El que resiste, gana
Aníbal sabía como conseguir la victoria, pero no cómo utilizarla
"Houston, tenemos un problema": los detalles y curiosidades tras uno de los mensajes de alarma más famosos de la historia
https://amaltea.wordpress.com/2008/03/06/proverbios-y-refranes-grecolatinos/
Bob_Ale

Desconectado Desconectado

Mensajes: 29


Ver Perfil
Re:
« Respuesta #5 en: 12 Agosto 2015, 15:16 pm »

Te has asegurado que no es algún móvil,  tablet,  etc...  tuyo?

De todas formas yo apagaria todo todo,  incluido el router y reconfiguraria todos los accesos a tu red,  contraseñas,  filtros mac,  etc... Ponerlo todo más restrictivo.
Restablece todo y ve dando paso a tus dispositivos de uno en uno y poco a poco.

Y si aun así sigue entrando pues ir anotando datos de los accesos,  direcciones,  mac,  horas de acceso,  tráfico... Igual así puedes llegar a controlarlo e incluso bloquerlo.

Y paciencia...

Enviado desde mi GT-I9300 mediante Tapatalk
En línea

Bob_Ale

Desconectado Desconectado

Mensajes: 29


Ver Perfil
Re:
« Respuesta #6 en: 12 Agosto 2015, 15:29 pm »

Recuerdo que en algún router se puede incluso bloquear el acceso a ciertas direcciones mac.

Por otro lado,  teniendo la Mac podrías localizar la IP y de ahi ya tendras más posibilidades de acceso al propio dispositivo atacante.

Enviado desde mi GT-I9300 mediante Tapatalk
En línea

engel lex
Moderador Global
***
Desconectado Desconectado

Mensajes: 15.514



Ver Perfil
Re:
« Respuesta #7 en: 12 Agosto 2015, 15:33 pm »

Recuerdo que en algún router se puede incluso bloquear el acceso a ciertas direcciones mac.

Por otro lado,  teniendo la Mac podrías localizar la IP y de ahi ya tendras más posibilidades de acceso al propio dispositivo atacante.

Enviado desde mi GT-I9300 mediante Tapatalk

XD

no diré más...
En línea

El problema con la sociedad actualmente radica en que todos creen que tienen el derecho de tener una opinión, y que esa opinión sea validada por todos, cuando lo correcto es que todos tengan derecho a una opinión, siempre y cuando esa opinión pueda ser ignorada, cuestionada, e incluso ser sujeta a burla, particularmente cuando no tiene sentido alguno.
Hason


Desconectado Desconectado

Mensajes: 787


Keep calm and use the spiritual force


Ver Perfil WWW
Re: que puedo hacer teniendo la MAC de un atacante?
« Respuesta #8 en: 12 Agosto 2015, 15:39 pm »

Tengo todo cerrado, está en mi pc, he conseguido un scan del host atacante con zenmap:


Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-12 15:26 CEST
NSE: Loaded 227 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 15:26
NSE: mtrace: A source IP must be provided through fromip argument.
Completed NSE at 15:26, 10.11s elapsed
Pre-scan script results:
| broadcast-eigrp-discovery:
|_ ERROR: Couldn't get an A.S value.
| broadcast-igmp-discovery:
|   222.222.222.26
|     Interface: eth1
|     Version: 2
|     Group: 224.0.0.252
|     Description: Link-local Multicast Name Resolution (rfc4795)
|   222.222.222.26
|     Interface: eth1
|     Version: 2
|     Group: 239.255.255.250
|     Description: Organization-Local Scope (rfc2365)
|_  Use the newtargets script-arg to add the results as targets
| http-icloud-findmyiphone:
|_  ERROR: No username or password was supplied
| http-icloud-sendmsg:
|_  ERROR: No username or password was supplied
| targets-asn:
|_  targets-asn.asn is a mandatory parameter
Initiating Parallel DNS resolution of 1 host. at 15:26
Completed Parallel DNS resolution of 1 host. at 15:26, 0.05s elapsed
Initiating SYN Stealth Scan at 15:26
Scanning 0.0.0.0 [1000 ports]
SYN Stealth Scan Timing: About 30.30% done; ETC: 15:28 (0:01:11 remaining)
SYN Stealth Scan Timing: About 60.05% done; ETC: 15:28 (0:00:41 remaining)
Completed SYN Stealth Scan at 15:28, 101.14s elapsed (1000 total ports)
Initiating UDP Scan at 15:28
Scanning 0.0.0.0 [1000 ports]
adjust_timeouts2: packet supposedly had rtt of -177908 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -177908 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102257 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102257 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102213 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102213 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102168 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102168 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102123 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102123 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102079 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102079 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102034 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102034 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101988 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101988 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101941 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101941 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101896 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101896 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101851 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101851 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101804 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101804 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101758 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101758 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101706 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101706 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101590 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101590 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100197 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100197 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100156 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100156 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100113 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100113 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100027 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -100027 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103356 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103356 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103317 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103317 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103277 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103277 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103226 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103226 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103188 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103188 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103152 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103152 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103114 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103114 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103077 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103077 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103039 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103039 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103001 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103001 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102962 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102962 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102925 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102925 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102889 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102889 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102850 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102850 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102811 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102811 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102774 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102774 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102738 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102738 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102700 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102700 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102662 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102662 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102623 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102623 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102585 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102585 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102547 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102547 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102510 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102510 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102472 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102472 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102434 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102434 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102397 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102397 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102359 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102359 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102323 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102323 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102284 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102284 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102247 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102247 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102209 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102209 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102171 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102171 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102133 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102133 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102094 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102094 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102056 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102056 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102020 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102020 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101983 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101983 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101946 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101946 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101905 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101905 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101868 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101868 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101829 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101829 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101788 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101788 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101750 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101750 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101712 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101712 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101674 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101674 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101592 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -101592 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103459 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103459 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103420 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103420 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103382 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103382 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103343 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103343 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103302 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103302 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103247 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103247 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103164 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103164 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103127 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103127 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103089 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103089 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103051 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103051 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103012 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -103012 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102973 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102973 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102933 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102933 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102893 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102893 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102855 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102855 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102816 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102816 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102779 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102779 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102740 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102740 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102700 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102700 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102660 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102660 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102620 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102620 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102581 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102581 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102545 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102545 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102507 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102507 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102471 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102471 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102434 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102434 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102396 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102396 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102359 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102359 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102321 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102321 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102269 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -102269 microseconds.  Ignoring time.
Completed UDP Scan at 15:28, 3.38s elapsed (1000 total ports)
Initiating Service scan at 15:28
Scanning 3 services on 0.0.0.0
Service scan Timing: About 33.33% done; ETC: 15:32 (0:02:46 remaining)
Completed Service scan at 15:29, 82.55s elapsed (3 services on 1 host)
Initiating OS detection (try #1) against 0.0.0.0
Retrying OS detection (try #2) against 0.0.0.0
NSE: Script scanning 0.0.0.0.
Initiating NSE at 15:29
Completed NSE at 15:30, 30.46s elapsed
Nmap scan report for 0.0.0.0
Host is up (0.098s latency).
Not shown: 1997 filtered ports
PORT     STATE         SERVICE  VERSION
68/udp   open|filtered dhcpc
631/udp  open|filtered ipp
5353/udp open|filtered zeroconf
Too many fingerprints match this host to give specific OS details
Network Distance: 0 hops

Host script results:
|_asn-query: No Such Name
|_hostmap-robtex:
| ip-geolocation-geoplugin:
| 0.0.0.0
|   coordinates (lat,lon): 0,0
|_  state: Unknown,
|_ip-geolocation-maxmind: ERROR: Script execution failed (use -d to debug)
| whois: Record found at whois.arin.net
| netrange: 0.0.0.0 - 0.255.255.255
| netname: SPECIAL-IPV4-LOCAL-ID-IANA-RESERVED
| orgname: Internet Assigned Numbers Authority
| orgid: IANA
| country: US stateprov: CA
|
| orgtechname: ICANN
|_orgtechemail: abuse@iana.org

NSE: Script Post-scanning.
Read data files from: /usr/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 232.60 seconds
           Raw packets sent: 3150 (126.387KB) | Rcvd: 1117 (67.379KB)



Tiene abiertos los siguientes puertos:


68 udp  open/filtered  dhcpc
631 udp  open/filtered  ipp
5353 udp  open/filtered zeroconf

Decidme algo de que hacer con esto, y las direcciones, ¿puedo atacarle por un puerto y sacar más información?
No se como hacerlo, algún encaminamiento.
Lo de escanear las ip, estoy harto de hacerlo, no me lleva a ningún sitio, siempre las va cambiando, y me llevan a diferentes sitios siempre, necesito algún ataque más directo para saber más.

Un saludo.
En línea

Verse constantemente expuesto al peligro puede generar desprecio hacia él.
El que resiste, gana
Aníbal sabía como conseguir la victoria, pero no cómo utilizarla
"Houston, tenemos un problema": los detalles y curiosidades tras uno de los mensajes de alarma más famosos de la historia
https://amaltea.wordpress.com/2008/03/06/proverbios-y-refranes-grecolatinos/
simorg
Ex-Staff
*
Desconectado Desconectado

Mensajes: 8.302



Ver Perfil
Re: que puedo hacer teniendo la MAC de un atacante?
« Respuesta #9 en: 12 Agosto 2015, 15:48 pm »

Hola, esto es lo que has puesto:

http://foro.elhacker.net/home/y/Desktop/toma con mac ajena.png[/img]
http://foro.elhacker.net/home/y/Desktop/detalle mac ajena.png[/img]
http://foro.elhacker.net/home/y/Desktop/macs ajenas.png[/img]
http://foro.elhacker.net/home/y/Desktop/mac duplicada.png[/img]
http://foro.elhacker.net/home/y/Desktop/duplicate use mac detalle.png[/img]

Eso no se hace así......primero tienes que subir las imagenes a un hosting exterior, alli coges la url que te daran para cada imagen y la colocas aquí..... :P

Puedes usar este: http://postimage.org/

No es que tu "Cracker" no te deje subir las imagenes, es que no tienes ni idea de como se hace...... :P


Saludos.
« Última modificación: 12 Agosto 2015, 15:53 pm por simorg » En línea

Páginas: [1] 2 Ir Arriba Respuesta Imprimir 

Ir a:  

WAP2 - Aviso Legal - Powered by SMF 1.1.21 | SMF © 2006-2008, Simple Machines