Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: Fresh installed Ubuntu infected - continued, now with logs

  1. #1
    Join Date
    Jul 2006
    Beans
    79
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Fresh installed Ubuntu infected - continued, now with logs

    Hi again.

    I have beaten my personal record by being able to use an Ubuntu desktop 8.04.1 fully updated for a week, but nothing lasts forever

    Code:
    ** Alert 1222554996.8360: mail  - ossec,rootcheck,
    2008 Sep 28 00:36:36 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    Port '953'(tcp) hidden. Kernel-level rootkit or trojaned version of netstat.
    This is around 15 reinstalls in 5 weeks, I have lost track of the exact number.
    This time the attack destroyed my LUKS password like many times before, but first I managed to get logs.

    I have /bin, /etc, /proc, /tmp and /var, when I tried to copy /usr/bin the attack locked the computer.

    As I previously have mentioned, I am no security expert, but I would be better off if I was one, as these attackers are very persistent.

    I will be very thankful if someone will direct me through the forensics. I will deliver all evidence I have on request, so this very annoying vulnerability can be solved. It has now cost me 5 weeks of ordinary work.

    I have collected a total of 1.9 GByte of data for this single attack, and I will post whatever logged data you find important.

    The only thing I can trust for the moment is the CD from www.polippix.org.

    Here is the first place I suspect the attack succeeded. Clipped from /var/log/syslog.

    Code:
    Sep 27 10:16:13 ht41 NetworkManager: <info>  DHCP daemon state is now 3 (renew) for interface eth0 
    Sep 27 10:16:13 ht41 dhclient: bound to 192.168.10.81 -- renewal in 50 seconds.
    Sep 27 10:17:01 ht41 /USR/SBIN/CRON[12217]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
    Sep 27 10:17:03 ht41 dhclient: DHCPREQUEST of <null address> on eth0 to 192.168.10.7 port 67
    Sep 27 10:17:03 ht41 dhclient: DHCPACK of 192.168.10.81 from 192.168.10.7
    Sep 27 10:17:03 ht41 NetworkManager: <info>  DHCP daemon state is now 3 (renew) for interface eth0 
    Sep 27 10:17:03 ht41 dhclient: bound to 192.168.10.81 -- renewal in 52 seconds.
    Sep 27 10:17:55 ht41 dhclient: DHCPREQUEST of <null address> on eth0 to 192.168.10.7 port 67
    Sep 27 10:17:55 ht41 dhclient: DHCPACK of 192.168.10.81 from 192.168.10.7
    Sep 27 10:17:55 ht41 NetworkManager: <info>  DHCP daemon state is now 3 (renew) for interface eth0 
    Sep 27 10:17:55 ht41 dhclient: bound to 192.168.10.81 -- renewal in 45 seconds.
    Sep 27 10:18:40 ht41 dhclient: DHCPREQUEST of <null address> on eth0 to 192.168.10.7 port 67
    Sep 27 10:18:40 ht41 dhclient: DHCPACK of 192.168.10.81 from 192.168.10.7
    Sep 27 10:18:40 ht41 NetworkManager: <info>  DHCP daemon state is now 3 (renew) for interface eth0 
    Sep 27 10:18:40 ht41 dhclient: bound to 192.168.10.81 -- renewal in 44 seconds.
    Sep 27 10:18:56 ht41 anacron[12490]: Anacron 2.3 started on 2008-09-27
    Sep 27 10:18:56 ht41 anacron[12490]: Normal exit (0 jobs run)
    Sep 27 10:19:24 ht41 dhclient: DHCPREQUEST of <null address> on eth0 to 192.168.10.7 port 67
    Sep 27 10:19:24 ht41 dhclient: DHCPACK of 192.168.10.81 from 192.168.10.7
    Sep 27 10:19:24 ht41 NetworkManager: <info>  DHCP daemon state is now 3 (renew) for interface eth0 
    Sep 27 10:19:24 ht41 dhclient: bound to 192.168.10.81 -- renewal in 55 seconds.
    Sep 27 10:19:31 ht41 kernel: [68179.062580] e1000: eth0: e1000_watchdog: NIC Link is Down
    Sep 27 10:19:31 ht41 NetworkManager: <info>  SWITCH: terminating current connection 'eth0' because it's no longer valid. 
    Sep 27 10:19:31 ht41 NetworkManager: <info>  Deactivating device eth0. 
    Sep 27 10:19:31 ht41 dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 16126
    Sep 27 10:19:31 ht41 dhclient: killed old client process, removed PID file
    Sep 27 10:19:31 ht41 dhclient: DHCPRELEASE on eth0 to 192.168.10.7 port 67
    Sep 27 10:19:31 ht41 avahi-daemon[5057]: Withdrawing address record for 192.168.10.81 on eth0.
    Sep 27 10:19:31 ht41 avahi-daemon[5057]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.10.81.
    Sep 27 10:19:31 ht41 avahi-daemon[5057]: Interface eth0.IPv4 no longer relevant for mDNS.
    Sep 27 10:19:31 ht41 dhcdbd:  dhclient 16126 down (9) but si_code == 0 and releasing==0 !
    Sep 27 10:19:32 ht41 avahi-daemon[5057]: Withdrawing address record for fe80::211:25ff:fe2d:29d2 on eth0.
    Sep 27 10:19:32 ht41 NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
    Sep 27 10:19:32 ht41 NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
    Sep 27 10:19:41 ht41 kernel: [181955.128740] e1000: eth0: e1000_watchdog: NIC Link is Up 10 Mbps Half Duplex, Flow Control: None
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link. 
    Sep 27 10:19:41 ht41 kernel: [181955.130044] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    Sep 27 10:19:41 ht41 NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'. 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Will activate connection 'eth0'. 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Device eth0 activation scheduled... 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) started... 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started... 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete. 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting... 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful. 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete. 
    Sep 27 10:19:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started... 
    Sep 27 10:19:42 ht41 NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction. 
    Sep 27 10:19:42 ht41 dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
    Sep 27 10:19:42 ht41 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. 
    Sep 27 10:19:42 ht41 NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0 
    Sep 27 10:19:43 ht41 avahi-daemon[5057]: Registering new address record for fe80::211:25ff:fe2d:29d2 on eth0.*.
    Sep 27 10:19:43 ht41 NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0 
    Sep 27 10:19:47 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
    Sep 27 10:19:52 ht41 kernel: [181958.102779] eth0: no IPv6 routers present
    Sep 27 10:19:54 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
    Sep 27 10:20:03 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
    Sep 27 10:20:15 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
    Sep 27 10:20:33 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
    Sep 27 10:20:42 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
    Sep 27 10:20:48 ht41 dhclient: No DHCPOFFERS received.
    
    Sep 27 10:20:48 ht41 avahi-autoipd(eth0)[12696]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
    
    
    Sep 27 10:20:48 ht41 avahi-autoipd(eth0)[12696]: Successfully called chroot().
    
    Sep 27 10:20:48 ht41 avahi-autoipd(eth0)[12696]: Successfully dropped root privileges.
    Sep 27 10:20:48 ht41 avahi-autoipd(eth0)[12696]: Starting with address 169.254.5.161
    Sep 27 10:20:53 ht41 avahi-autoipd(eth0)[12696]: Callout BIND, address 169.254.5.161 on interface eth0
    Sep 27 10:20:53 ht41 avahi-daemon[5057]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.5.161.
    Sep 27 10:20:53 ht41 avahi-daemon[5057]: New relevant interface eth0.IPv4 for mDNS.
    Sep 27 10:20:53 ht41 avahi-daemon[5057]: Registering new address record for 169.254.5.161 on eth0.IPv4.
    Like my OpenBSD attacked, also Ubuntu has lots of DHCPREQUEST preceeding the attack succeeding, But whether this is significant, I can't tell.

    Please help.

  2. #2
    Join Date
    Jul 2006
    Beans
    79
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Fresh installed Ubuntu infected - continued, now with logs

    Although I have 1.9 GByte collected from the disk, it vould be nice to get LUKS on the infected disk working again.

    When I first installed the Ubuntu, after getting the system updated and operational, I used dd to make a verbatim copy of the harddisk to another identical type harddisk.

    I then stored the original disk and inserted the copy for further use, and it is the copy that is infected and unable to be opened with LUKS.

    I wonder if is is possible to copy a limited number of blocks from the original disk to make LUKS work again on the infected disk. Do anyone know how many blocks I must copy from the beginning of the disk using dd ?

    It appears an extra hidden file system has been added, see last code list.

    The computer was installed:

    Code:
    Log started: 2008-09-16  13:56:41
    Selecting previously deselected package dmsetup.
    (Reading database ... 8617 files and directories currently installed.)
    Unpacking dmsetup (from .../dmsetup_1.02.20-2ubuntu2_i386.deb) ...
    Selecting previously deselected package cryptsetup.
    Unpacking cryptsetup (from .../cryptsetup_1.0.5-2ubuntu12_i386.deb) ...
    Setting up dmsetup (2:1.02.20-2ubuntu2) ...
    update-initramfs: deferring update (trigger activated)
    From /var/log/daemon.log I have copied a sequence showing the last normal DHCP assignment and then the first assignment to 169.254.5.161

    Sep 26 01:09:12 ht41 avahi-daemon[5057]: Withdrawing address record for 192.168.10.81 on eth0.
    and
    Sep 26 01:35:27 ht41 avahi-autoipd(eth0)[31049]: Callout BIND, address 169.254.5.161 on interface eth0

    What is going on here ?

    In a previous post someone thought I was doing this for fun, because I was not able to show logs.

    It is not funny, and I now have lots of logs and data, please help, please.

    Before I discovered this new attack, I had just finished an install of an Ubuntu server, just with NFS and subversion. It is my first server without desktop, attempting to have a more secure server.

    My T41 portable was setup as a subversion client, and succeeded a checkout of my backed up subversion database. With this last attack I can start all over again.

    Code:
    Sep 26 01:07:36 ht41 NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0 
    Sep 26 01:07:40 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
    Sep 26 01:07:40 ht41 dhclient: DHCPOFFER of 192.168.10.81 from 192.168.10.7
    Sep 26 01:07:40 ht41 dhclient: DHCPREQUEST of 192.168.10.81 on eth0 to 255.255.255.255 port 67
    Sep 26 01:07:40 ht41 dhclient: DHCPACK of 192.168.10.81 from 192.168.10.7
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.10.81.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: New relevant interface eth0.IPv4 for mDNS.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Registering new address record for 192.168.10.81 on eth0.IPv4.
    Sep 26 01:07:40 ht41 NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth0 
    Sep 26 01:07:40 ht41 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... 
    Sep 26 01:07:40 ht41 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started... 
    Sep 26 01:07:40 ht41 NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon: 
    Sep 26 01:07:40 ht41 NetworkManager: <info>    address 192.168.10.81 
    Sep 26 01:07:40 ht41 NetworkManager: <info>    netmask 255.255.255.0 
    Sep 26 01:07:40 ht41 NetworkManager: <info>    broadcast 192.168.10.255 
    Sep 26 01:07:40 ht41 NetworkManager: <info>    gateway 192.168.10.7 
    Sep 26 01:07:40 ht41 NetworkManager: <info>    nameserver 192.168.10.7 
    Sep 26 01:07:40 ht41 NetworkManager: <info>    domain name 'xxnone' 
    Sep 26 01:07:40 ht41 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... 
    Sep 26 01:07:40 ht41 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. 
    Sep 26 01:07:40 ht41 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... 
    Sep 26 01:07:40 ht41 dhclient: bound to 192.168.10.81 -- renewal in 58 seconds.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Withdrawing address record for 192.168.10.81 on eth0.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.10.81.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Interface eth0.IPv4 no longer relevant for mDNS.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Withdrawing address record for fe80::211:25ff:fe2d:29d2 on eth0.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.10.81.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: New relevant interface eth0.IPv4 for mDNS.
    Sep 26 01:07:40 ht41 avahi-daemon[5057]: Registering new address record for 192.168.10.81 on eth0.IPv4.
    Sep 26 01:07:41 ht41 NetworkManager: <info>  Clearing nscd hosts cache. 
    Sep 26 01:07:41 ht41 NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))  
    Sep 26 01:07:41 ht41 NetworkManager: <info>  Activation (eth0) successful, device activated. 
    Sep 26 01:07:41 ht41 NetworkManager: <info>  Activation (eth0) Finish handler scheduled. 
    Sep 26 01:07:41 ht41 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. 
    Sep 26 01:07:42 ht41 avahi-daemon[5057]: Registering new address record for fe80::211:25ff:fe2d:29d2 on eth0.*.
    Sep 26 01:07:45 ht41 ntpdate[28601]: adjust time server 91.189.94.4 offset -0.298091 sec
    Sep 26 01:08:38 ht41 dhclient: DHCPREQUEST of <null address> on eth0 to 192.168.10.7 port 67
    Sep 26 01:08:38 ht41 dhclient: DHCPACK of 192.168.10.81 from 192.168.10.7
    Sep 26 01:08:38 ht41 NetworkManager: <info>  DHCP daemon state is now 3 (renew) for interface eth0 
    Sep 26 01:08:38 ht41 dhclient: bound to 192.168.10.81 -- renewal in 50 seconds.
    Sep 26 01:09:05 ht41 rpc.statd[28979]: Version 1.1.2 Starting
    Sep 26 01:09:09 ht41 NetworkManager: <debug> [1222384149.214441] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_1205_noserial'). 
    Sep 26 01:09:09 ht41 NetworkManager: <debug> [1222384149.817265] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_1205_noserial_if0'). 
    Sep 26 01:09:09 ht41 NetworkManager: <debug> [1222384149.921943] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_1205_noserial_if0_logicaldev_input'). 
    Sep 26 01:09:12 ht41 NetworkManager: <info>  SWITCH: terminating current connection 'eth0' because it's no longer valid. 
    Sep 26 01:09:12 ht41 NetworkManager: <info>  Deactivating device eth0. 
    Sep 26 01:09:12 ht41 dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 28533
    Sep 26 01:09:12 ht41 dhclient: killed old client process, removed PID file
    Sep 26 01:09:12 ht41 dhclient: DHCPRELEASE on eth0 to 192.168.10.7 port 67
    Sep 26 01:09:12 ht41 avahi-daemon[5057]: Withdrawing address record for 192.168.10.81 on eth0.
    Sep 26 01:09:12 ht41 avahi-daemon[5057]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.10.81.
    Sep 26 01:09:12 ht41 avahi-daemon[5057]: Interface eth0.IPv4 no longer relevant for mDNS.
    Sep 26 01:09:13 ht41 avahi-daemon[5057]: Withdrawing address record for fe80::211:25ff:fe2d:29d2 on eth0.
    Sep 26 01:09:13 ht41 NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
    Sep 26 01:09:13 ht41 NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
    Sep 26 01:30:24 ht41 rpc.statd[28979]: Caught signal 15, un-registering and exiting.
    Sep 26 01:30:29 ht41 rpc.statd[30614]: Version 1.1.2 Starting
    Sep 26 01:30:29 ht41 rpc.statd[30614]: unable to register (statd, 1, udp).
    Sep 26 01:31:05 ht41 NetworkManager: <debug> [1222385465.805798] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_1205_noserial_if0_logicaldev_input'). 
    Sep 26 01:31:05 ht41 NetworkManager: <debug> [1222385465.820040] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_1205_noserial_if0'). 
    Sep 26 01:31:05 ht41 NetworkManager: <debug> [1222385465.826053] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/usb_device_5e3_1205_noserial'). 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link. 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'. 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Will activate connection 'eth0'. 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Device eth0 activation scheduled... 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) started... 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started... 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete. 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting... 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful. 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete. 
    Sep 26 01:34:17 ht41 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started... 
    Sep 26 01:34:18 ht41 NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction. 
    Sep 26 01:34:18 ht41 dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
    Sep 26 01:34:18 ht41 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. 
    Sep 26 01:34:18 ht41 NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0 
    Sep 26 01:34:18 ht41 avahi-daemon[5057]: Registering new address record for fe80::211:25ff:fe2d:29d2 on eth0.*.
    Sep 26 01:34:19 ht41 NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0 
    Sep 26 01:34:21 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
    Sep 26 01:34:27 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
    Sep 26 01:34:34 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
    Sep 26 01:34:42 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
    Sep 26 01:35:03 ht41 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19
    Sep 26 01:35:22 ht41 dhclient: No DHCPOFFERS received.
    Sep 26 01:35:22 ht41 avahi-autoipd(eth0)[31049]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 113).
    Sep 26 01:35:22 ht41 avahi-autoipd(eth0)[31049]: Successfully called chroot().
    Sep 26 01:35:22 ht41 avahi-autoipd(eth0)[31049]: Successfully dropped root privileges.
    Sep 26 01:35:22 ht41 avahi-autoipd(eth0)[31049]: Starting with address 169.254.5.161
    Sep 26 01:35:27 ht41 avahi-autoipd(eth0)[31049]: Callout BIND, address 169.254.5.161 on interface eth0
    Sep 26 01:35:27 ht41 avahi-daemon[5057]: Joining mDNS multicast group on interface eth0.IPv4 with address 169.254.5.161.
    Sep 26 01:35:27 ht41 avahi-daemon[5057]: New relevant interface eth0.IPv4 for mDNS.
    Sep 26 01:35:27 ht41 avahi-daemon[5057]: Registering new address record for 169.254.5.161 on eth0.IPv4.
    Sep 26 01:35:31 ht41 avahi-autoipd(eth0)[31049]: Successfully claimed IP address 169.254.5.161
    Sep 26 01:35:32 ht41 NetworkManager: <info>  DHCP daemon state is now 9 (fail) for interface eth0 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Timeout) started... 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  No DHCP reply received.  Automatically obtaining IP via Zeroconf. 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  avahi-autoipd running on eth0, assuming IPv4LL address 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Timeout) complete. 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  not touching eth0 configuration, was configured externally 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) successful, device activated. 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  DHCP daemon state is now 14 (normal exit) for interface eth0 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) Finish handler scheduled. 
    Sep 26 01:35:32 ht41 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. 
    Sep 26 01:35:37 ht41 avahi-autoipd(eth0)[31049]: A routable address has been configured.
    Sep 26 01:35:37 ht41 avahi-autoipd(eth0)[31049]: Callout UNBIND, address 169.254.5.161 on interface eth0
    Sep 26 01:35:37 ht41 avahi-daemon[5057]: Leaving mDNS multicast group on interface eth0.IPv4 with address 169.254.5.161.
    Sep 26 01:35:37 ht41 avahi-daemon[5057]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.10.33.
    Sep 26 01:35:37 ht41 avahi-daemon[5057]: Registering new address record for 192.168.10.33 on eth0.IPv4.
    Sep 26 01:35:37 ht41 avahi-daemon[5057]: Withdrawing address record for 169.254.5.161 on eth0.
    Sep 26 01:35:52 ht41 ntpdate[31094]: can't find host ntp.ubuntu.com 
    Sep 26 01:35:52 ht41 ntpdate[31094]: no servers can be used, exiting
    Ossec log:

    Code:
    ** Alert 1222554500.0: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/dhclient.eth0.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.268: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/rpc.statd.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.534: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/sm-notify.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.800: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/portmap_mapping' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.1068: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/sudo/fefekh/1' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.1335: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/sudo/fefekh/0' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.1602: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/sudo/fefekh/unknown' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.1875: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/console/fefekh' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.2143: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/crond.reboot' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.2409: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/crond.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.2672: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/gdm.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.2933: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/console-kit-daemon.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.3209: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/hald/acl-list' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.3476: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/hald/hald.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.3743: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/dhcdbd.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.4007: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/hotkey-setup' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.4273: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/cups/printcap' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.4540: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/avahi-daemon/checked_nameservers' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.4826: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/avahi-daemon/pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.5096: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/system-tools-backends.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.5375: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/NetworkManager/NetworkManagerDispatcher.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.5672: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/NetworkManager/NetworkManager.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.5959: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/dbus/pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.6221: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/klogd/klogd.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.6490: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/klogd/kmsgpipe.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.6762: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/syslogd.pid' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.7027: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/PolicyKit/user-fefekh.auths' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.7308: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/motd' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.7566: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/utmp' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.7824: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/network/ifstate' present on /dev. Possible hidden file.
    
    ** Alert 1222554500.8093: mail  - ossec,rootcheck,
    2008 Sep 28 00:28:20 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    File '/dev/shm/var.run/sendsigs.omit' present on /dev. Possible hidden file.
    
    ** Alert 1222554996.8360: mail  - ossec,rootcheck,
    2008 Sep 28 00:36:36 ht41->rootcheck
    Rule: 510 (level 7) -> 'Host-based anomaly detection event (rootcheck).'
    Src IP: (none)
    User: (none)
    Port '953'(tcp) hidden. Kernel-level rootkit or trojaned version of netstat.
    
    ** Alert 1222556559.8627: mail  - syslog,errors,
    2008 Sep 28 01:02:39 ht41->/var/log/syslog
    Rule: 1002 (level 2) -> 'Unknown problem somewhere in the system.'
    Src IP: (none)
    User: (none)
    Sep 28 01:02:38 ht41 NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
    
    ** Alert 1222556559.8912: mail  - syslog,errors,
    2008 Sep 28 01:02:39 ht41->/var/log/syslog
    Rule: 1002 (level 2) -> 'Unknown problem somewhere in the system.'
    Src IP: (none)
    User: (none)
    Sep 28 01:02:38 ht41 NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
    
    ** Alert 1222557761.9198: - syslog,sudo
    2008 Sep 28 01:22:41 ht41->/var/log/auth.log
    Rule: 5402 (level 3) -> 'Successful sudo to ROOT executed'
    Src IP: (none)
    User: fefekh
    Sep 28 01:22:41 ht41 sudo:   fefekh : TTY=pts/0 ; PWD=/home/fefekh ; USER=root ; COMMAND=/bin/su
    
    ** Alert 1222557761.9468: - pam,syslog,authentication_success,
    2008 Sep 28 01:22:41 ht41->/var/log/auth.log
    Rule: 5501 (level 3) -> 'Login session opened.'
    Src IP: (none)
    User: (none)
    Sep 28 01:22:41 ht41 sudo: pam_unix(sudo:session): session opened for user root by fefekh(uid=0)
    
    ** Alert 1222557761.9750: - pam,syslog,
    2008 Sep 28 01:22:41 ht41->/var/log/auth.log
    Rule: 5502 (level 3) -> 'Login session closed.'
    Src IP: (none)
    User: (none)
    Sep 28 01:22:41 ht41 sudo: pam_unix(sudo:session): session closed for user root
    
    ** Alert 1222557761.9992: - syslog, su,authentication_success,
    2008 Sep 28 01:22:41 ht41->/var/log/auth.log
    Rule: 5303 (level 3) -> 'User successfully changed UID to root.'
    Src IP: (none)
    User: (none)
    Sep 28 01:22:41 ht41 su[27516]: + pts/0 root:root
    
    ** Alert 1222557761.10244: - syslog, su,authentication_success,
    2008 Sep 28 01:22:41 ht41->/var/log/auth.log
    Rule: 5303 (level 3) -> 'User successfully changed UID to root.'
    Src IP: (none)
    User: (none)
    Sep 28 01:22:41 ht41 su[27516]: pam_unix(su:session): session opened for user root by fefekh(uid=0)

  3. #3
    Join Date
    Oct 2006
    Location
    SLC, UofU
    Beans
    684
    Distro
    Kubuntu Jaunty Jackalope (testing)

    Re: Fresh installed Ubuntu infected - continued, now with logs

    There is absolutely nothing in any of the 3 posted logs that indicates a hack. It does look like there may be a problem with your interface (eth0) or dhcp server, such that your connection fails and attempts to reconnect. Do 2 machines on your network have the same IP address? Is your etheret cable in good condition?
    _
    Your ossec logs may seem scary at a few points, but a quick google showed that they are normal false positives on Debian distros.
    _

    Please post more logs that contain information that concerns you, I'll address them as I'm able.
    _

    I suggest that you disable your wireless interface until you feel that your concerns have been addressed sufficiently.
    --Superb--

  4. #4
    Join Date
    Jul 2006
    Beans
    79
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Fresh installed Ubuntu infected - continued, now with logs

    Quote Originally Posted by wirelessmonkey View Post
    There is absolutely nothing in any of the 3 posted logs that indicates a hack. It does look like there may be a problem with your interface (eth0) or dhcp server, such that your connection fails and attempts to reconnect. Do 2 machines on your network have the same IP address? Is your etheret cable in good condition?
    I have 2 undeniable indications, that I have been attacked:

    1. I loose the ability as root to copy data from the harddisk to an usb device.
    2. Luks stops to work, In previous attacks vith the same behavior it is possible to use the computer if I don't try to access the logs. If I do, the permissions gets changed, so I cant mount usb devices, or copy to them, if already mounted. At next boot LUKS is broken.

    I have found that by only being connected to the internet while I need to communicate, prolongs the time to next attack. So when I constantly connect and disconnect the ethernet cable, then it is visible in the log. Sorry I did not mention this.

    Quote Originally Posted by wirelessmonkey View Post
    _
    Your ossec logs may seem scary at a few points, but a quick google showed that they are normal false positives on Debian distros.
    If they are false positives, I don't have much clue where to look. Perhaps I should make a new install without LUKS.


    Quote Originally Posted by wirelessmonkey View Post
    Please post more logs that contain information that concerns you, I'll address them as I'm able.
    Thank you very much, unfortunately I have no experience in where to look. I will study more logs and post what I find suspecious.
    _
    Quote Originally Posted by wirelessmonkey View Post
    I suggest that you disable your wireless interface until you feel that your concerns have been addressed sufficiently.
    I never use wireless internet because of the health hazard, an I'm lucky to not to live in a large city with high levels of "electrosmog". A German professor has stated that there is hard evidence that WiFi, 3G, DECT and GSM is harmful to human health. So security with wireless is no issue for me. The German car manufacturer BMW has addressed these issues.

    I saw that a 3G phone is able to cut DNA strings at 2,5% of max. allowed transmission power.

    http://www.der-mast-muss-weg.de/016dectWLAN01.htm

    The problem is lots of money for the telecommunication companies, that severely affects what truth is.

  5. #5
    Join Date
    Aug 2007
    Location
    Birmingham, UK
    Beans
    181
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Re: Fresh installed Ubuntu infected - continued, now with logs

    How did you install Ubuntu? Using Ubuntu's free-shipit discs are the best way to install a fresj clean ubuntu without problems. If you burned a disc, it might be corrupt or not burned correctly. By the way, you can file bugs at launchpad.
    My Rig:
    [SIZE="1"]Intel Core 2 Quad Extreme QX9770 (12M Cache, 3.20 GHz, 1600 MHz FSB)
    Swiftech H20-220 Apex Ultra+ Water Cooling System 6072 GB RAM
    2TB SATA HD , Nvidia Geforce 8800GTX 512MB

  6. #6
    Join Date
    Jul 2006
    Beans
    79
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Fresh installed Ubuntu infected - continued, now with logs

    Quote Originally Posted by Amarsingh0793 View Post
    How did you install Ubuntu? Using Ubuntu's free-shipit discs are the best way to install a fresj clean ubuntu without problems. If you burned a disc, it might be corrupt or not burned correctly. By the way, you can file bugs at launchpad.
    Thank you for the advice, unfortunately I can not point out a bug.

    Install procedure:

    I download the alternate 8.04.1 .iso and the checksums. The checksums is additionally downloaded with Tor (www.polippix.org) just to be sure they are correct.

    I burn the iso and do a md5sum and verify.

    Before I install, I check the CD for defects, so I'm sure it reads correctly on the actual computer.

    The install is done without internet connected.

    I do some hardening stuff (kernel and TCP stack), and remove some user accounts from /etc/passwd

    I modify /etc/apt/sources.list, so it is like it was installed with internet connected.

    internet connected:

    apt-get update
    apt-get upgrade
    apt-get dist-upgrade

    apt-get install libc6 (needed by ossec)

    internet disconnected:

    Install a checksum verified Ossec 1.6 as stand alone.

    Internet connected:

    Installed Thunderbird, noscript, adblock plus.
    Restore the Thunderbird database.

    Installed NFS
    Installed RapidSVN
    used netstat to verify I have no open ports.
    Installed fwbuilder and installed the compiled script to run at boot time.

    Internet disconnected:


    Turn off power.

    Remove original harddisk

    Boot from 8.04.1 live CD

    usb mount harddisk seen as /dev/sda (original)
    usb mount extra HW identical harddisk seen as /dev/sdb (copy)

    dd if=/dev/sda of=/dev/sdb bs=16384 (verbatim disk copy)

    store the original harddisk for later use

    insert the copy for use in the computer
    Boot from the copy harddisk

    Wait for the attack to happen, If connected to the internet all the time, this happens in less than a day.

    I have seen this specific attack type behavior on:

    A Medion MD40100
    A Lenovo T30
    A Lenovo T41

    And also one OpenBSD 4.3 install did not stand the pressure. I have to say it was an extended install, to be useful.

    I also suffered from a ssh attack to my server 6 weeks ago. This server had an Ubuntu desktop, not so smart, and also I did trust the original install without using netstat. I had been running for about 6 months before attacked.

  7. #7
    Join Date
    Sep 2007
    Beans
    68
    Distro
    Ubuntu 7.10 Gutsy Gibbon

    Re: Fresh installed Ubuntu infected - continued, now with logs

    The avahi and dhcpclient logs are exactly how they would expect to be if an interface loses connectivity. The interface goes down and when it is seen to be back up again it tries to get its old IP reservation back. In the logs, no DHCP server responds, so dhcpclient gives an address in the 169.xxx.xxx.xxx range (which is reserved for hosts that can't get an IP address any other way).

    Your issues may both be harddrive issues that don't present themselves until the system has been running for a while (maybe because there is some bug using dd and using IDE drives in a USB interface???)

    1) When you say you can't copy to USB devices, what error are you getting?

    2) Why aren't you using the original disk and storing the copy?
    Sean T Murray

  8. #8

    Re: Fresh installed Ubuntu infected - continued, now with logs

    Hi Ekh, I don't think you're being attacked, relax.

    You could check the integrity of your files (google is your friend) by creating md5sums for all your files before and after the general failure, then check which have changed.

    Also, forget about luks until you have a working setup.

  9. #9
    Join Date
    Jul 2006
    Beans
    79
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Fresh installed Ubuntu infected - continued, now with logs

    Quote Originally Posted by stmurray View Post
    The avahi and dhcpclient logs are exactly how they would expect to be if an interface loses connectivity. The interface goes down and when it is seen to be back up again it tries to get its old IP reservation back. In the logs, no DHCP server responds, so dhcpclient gives an address in the 169.xxx.xxx.xxx range (which is reserved for hosts that can't get an IP address any other way).

    Your issues may both be harddrive issues that don't present themselves until the system has been running for a while (maybe because there is some bug using dd and using IDE drives in a USB interface???)

    1) When you say you can't copy to USB devices, what error are you getting?

    2) Why aren't you using the original disk and storing the copy?
    Thank you for interpreting the DHCP logs.

    The harddisks are 2 weeks old, but now I will use the original as it is.
    I bought 4 identical disks 2.5 inch Hitachi 160GB, I have many disk like these and have used then for more than a year without problems, and they behave the same "failure".

    The same eror on more identical disks is possible but in my opinion unlikely.

    Your questions:

    1) I cant remember the exact error message, but it was something about the device not configured, but it worked OK on another Ubuntu.

    There have been some cases where root did not have permission to copy.

    And there was this latest try with the cp program from an Identical Ubuntu:

    Code:
    root@ht41:/media/disk-1# ./cp -r --copy-contents -L /bin /media/disk-2/bin
    root@ht41:/media/disk-1# ./cp -r --copy-contents -L /usr/bin /media/disk-2/usr/bin
    ./cp: cannot create directory `/media/disk-2/usr/bin': No such file or directory
    root@ht41:/media/disk-1# ./cp -r --copy-contents -L /usr/sbin /media/disk-2/usr/sbin
    ./cp: cannot create directory `/media/disk-2/usr/sbin': No such file or directory
    root@ht41:/media/disk-1#
    2) If I do that, I don't know if the copy was successful, I feel more confident making copies from the original.

    I will do a fresh install without LUKS on the disk I see as infected"copy", or maybe I should buy more disks so I maybe later can open the disk again.

    I did look up the document on LUKS and copied the 2 first blocks from the original harddisk to the copy harddisk, but it say that the password may be wrong.

    I have not tried to boot from the infected disk.

    I think it may be a problem with the selected keyboard. Remember I have Danish keyboard layout, and I'm not sure if the selected layout at boot time is identical to the layout when running with Danish language from the 8.04.1 desktop live CD.

    This is the layout used to input my password involving keys that are not identical on us and dk layouts.

  10. #10
    Join Date
    Jul 2006
    Beans
    79
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Fresh installed Ubuntu infected - continued, now with logs

    Quote Originally Posted by Yannick Le Saint kyncani View Post
    Hi Ekh, I don't think you're being attacked, relax.
    Thank you for your suggestions.

    I wish you were right on this one.

    Apart from the Ubuntu related stuff, I also see other problems.

    I have traded a lot on ebay for 3 years, no sweat. When my trouble started, I could not log into ebay, yahoo or my netbank.

    Using the polippix CD I can log into ebay, without Tor, no way, having entered my username and password, I just get a new login page.

    Also other surfing involving https does not work without Tor.

    Quote Originally Posted by Yannick Le Saint kyncani View Post
    You could check the integrity of your files (google is your friend) by creating md5sums for all your files before and after the general failure, then check which have changed.
    Sure, google is a very effective search machine, but also a very effective data miner with personal information. My friend...maybe...

    I checked synaptic, and there are several choices for integrity test, I installed debsums on the original harddisk. Do your system generate similar output ?

    The system is up to date.

    Quote Originally Posted by Yannick Le Saint kyncani View Post
    Also, forget about luks until you have a working setup.
    Except from ossec added, I have been running OK with LUKS since the 8.04 release, except from the last 5 weeks.

    Code:
    fefekh@ht41:~$ sudo debsums | grep FAILED
    debsums: no md5sums for at
    debsums: no md5sums for base-files
    debsums: no md5sums for binutils
    debsums: no md5sums for binutils-static
    debsums: no md5sums for bogofilter
    debsums: no md5sums for bzip2
    debsums: no md5sums for dosfstools
    debsums: no md5sums for ed
    debsums: no md5sums for gnupg
    debsums: no md5sums for gpgv
    debsums: no md5sums for initscripts
    debsums: no md5sums for installation-report
    debsums: no md5sums for klogd
    debsums: no md5sums for libbz2-1.0
    debsums: no md5sums for libgdbm3
    debsums: no md5sums for libncurses5
    debsums: no md5sums for libncursesw5
    /lib/modules/2.6.24-19-generic/modules.pcimap                             FAILED
    /lib/modules/2.6.24-19-generic/modules.dep                                FAILED
    /lib/modules/2.6.24-19-generic/modules.ieee1394map                        FAILED
    /lib/modules/2.6.24-19-generic/modules.usbmap                             FAILED
    /lib/modules/2.6.24-19-generic/modules.isapnpmap                          FAILED
    /lib/modules/2.6.24-19-generic/modules.inputmap                           FAILED
    /lib/modules/2.6.24-19-generic/modules.seriomap                           FAILED
    /lib/modules/2.6.24-19-generic/modules.alias                              FAILED
    /lib/modules/2.6.24-19-generic/modules.symbols                            FAILED
    debsums: no md5sums for mawk
    debsums: no md5sums for mime-support
    debsums: no md5sums for module-init-tools
    debsums: no md5sums for ncurses-base
    debsums: no md5sums for ncurses-bin
    debsums: no md5sums for netbase
    debsums: no md5sums for rsync
    debsums: no md5sums for startup-tasks
    debsums: no md5sums for strace
    debsums: no md5sums for sysklogd
    debsums: no md5sums for sysv-rc
    debsums: no md5sums for sysvutils
    debsums: no md5sums for ubuntu-keyring
    debsums: no md5sums for update-inetd
    debsums: no md5sums for whois
    debsums: no md5sums for xbase-clients
    debsums: no md5sums for xorg
    debsums: no md5sums for xserver-xorg
    debsums: no md5sums for xserver-xorg-input-all
    debsums: no md5sums for xserver-xorg-video-all
    debsums: no md5sums for xutils
    fefekh@ht41:~$

Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •