Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

  • Days Won



About Skinny

  • Rank
    Hak5 Zombie

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Huntsville, AL

Recent Profile Visitors

1,800 profile views
  1. Could you specify how often you have it capturing an image? I would like to do some testing as well to see the effect you are talking about.
  2. IT'S FIXED!!! This took a stupid amount of time to figure out for such a simple work around. Before heading down the path outlined below, be absolutely certain there is not some other issue keeping the Crab from connecting to C2. Problem: After initially connecting to C2 and running perfectly over WiFi, subsequent attempts to connect to the same AP using the same Screen Crab prove fruitless and do not work. This is due to wlan0 on the Screencrab not being up when C2 is invoked at boot. Solution: Take the case off of the screen crab. Connect to the screen crab's heade
  3. I changed some things today and it seemed to be working for awhile. Jumping back into this project a few days ago, I screwed up the c2 setup. When I started c2, for hostname I put the hostname of the computer and not the IP address of the computer. If you look at the last post: POST: C2 POST ERROR: java.net.UnknownHostException: Unable to resolve host Chippunk: No address associated with hostname| This got me thinking as to why it would give me that error. After correcting the mistake, it worked great on two different networks. After putting the case back together and restarting
  4. For anyone interested, once connected to the serial port, there is a bash file in /system/bin called crab. It has loads of function in there you can play around with like changing LED colors, wifi functions, and other helpful things. To run the function type: source crab After that just type the name of the function you want to run. To find out the functions just cat out the file. cat /system/bin/crab Looking through logs a little more today, I see the problem that is occurring: C2Run: C2 Thread starting| C2Device: C2 STARTUP SYNC| Util: exec [cat /proc/uptime | busybox aw
  5. @trunner It doesn't seem to make a difference whether it's plugged into battery or into a wall outlet through a transformer, the result is the same. @phrogg After it booted, I just pressed Enter and the prompt popped up. I'm using Windows with Putty. The prompt I get is pasted below after the last few lines of the boot sequence. [ 22.793488] init: avc: denied { set } for property=tmp.exec_ubus scontext=u:r:system_app:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service [ 22.930341] init: avc: denied { set } for property=tmp.exec_ubus scontext=u:r:realtek:s0 tcontext=
  6. No. I was just wondering why you have no other network interfaces showing up. Besides the plunder bug, do you have any other network interface available on the machine?
  7. I am curious if anyone has gotten the Inject Raw Frames feature at the bottom of the PineAP page to work. I have tried several different frame types and attempted to receive the transmission from several different boxes (Mint Linux running on a VM and Pentoo running on my laptop). I have PineAP running with no other options on and a fresh firmware load. I am attempting to send an RTS frame. I copied the hex from Wireshark as it appears below. 000012002e48000000308f09c000e7010000b400a20084fcac5ac95f3c37866ef748 The Inject Raw Frame module then said to take out the radio header in
  8. I've finally got it working! But it's an unusable solution for the field. I opened it up and used the serial connection header to connect to check the wireless interface. I fully connected the device with the micoSD card inserted and plugged through an HDMI connection. The results of looking at the network interfaces were as follows after a full boot: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope
  9. The battle continues. I now have 3 screen crabs that all have the same issue. After running them for the 1st time, they never seem to connect consistently again. I have tried many different avenues to get consistent behavior, but the fact remains that the screen crab does not connect to the AP. I've tried 2 separate APs with similar results. Here is what is happening over the air. The screen crab will send out a Wildcard probe request, the AP will respond, and that's about all that happens. After that, the crab just starts sending out probe requests again. This sequence repeats all t
  10. Just to follow this up, usually this behavior will occur if you have the HDMI input and output switched on the crab.
  11. Are you feeding the signal into a monitor, a TV, or something else?
  12. Meanwhile, I'm still having trouble with the WiFi radio. I now have 3 screen crabs in my possession. I grabbed a brand new one and placed an SD card inside of it with a config file, containing just the WIFI SSID and password, and the device.config file from c2. The screen crab worked great. It connected to the AP and called back to C2 perfectly. After letting it grab a few screenshots over the course of several minutes, I pressed the button and let the light go green. I removed the microSD letting the light go red. I disconnected power from the crab. Next, I placed the microSD back into t
  13. Instead of editing it, erase everything in the file except for the WiFi SSID and Password. The only reason I say this is because of the line under #3 on the screen crab instructional page: https://docs.hak5.org/hc/en-us/articles/360033503594-Configuring-Screen-Crab-for-Cloud-C2 See if it makes a difference. Also, after you change it, let it fully reboot, press the button, let the LED turn green, unplug power, and then boot it again. I've found that sometimes it takes 2 boots before things start working. I'm not sure why.
  14. @zenn1999 Mine also gets very warm. It started out working two days ago when I set it up for another infrastructure, and then stopped working yesterday. I went into the office and grabbed two more. I'll test them Monday to see if they are having the same problem and get back to you.
  • Create New...