Comment on Thousands of private camera footages from bedrooms hacked, sold online - VnExpress International

• 520@kbin.social ⁨6⁩ ⁨months⁩ ago

  No I don't. Like the first example above I can simply trojanise an executable, and release it to the public.

  Once I'm on your network, the first thing I'm going to do is see what I'm working with. That means a network and system info sweep. If I'm efficient, I already have a script to do this.

  That sweep will reveal the presence of the camera. I might be interested in extortion material or I can sell this to a criminal gang, if I can get it open. I already have the camera's MAC address, so finding the make and model isn't too hard.

  Then I might browse to it, see what system software it is running. Then I would try default usernames and passwords (people don't always change them) and see if there are any usable exploits on the software.

  If I come across a certain camera type with certain vulnerabilities a lot, making a script to autofuck these cameras is child's play.

  source

  • ihavenopeopleskills@kbin.social ⁨6⁩ ⁨months⁩ ago

    What is the recommended on-ramp for someone with a CS degree and a networking background?

    source

    • 520@kbin.social ⁨6⁩ ⁨months⁩ ago

      With that kind of background you've got a good advantage. You probably know how people fuck up their implementations as rookies, the next step is learning to take advantage of it.

      Depending on the areas you want to get into (web, mobile, infrastructure, web3, etc) there are a lot of different training materials you can do.

      Basic infrastructure stuff is a must, but it's really simple. Your main tool for this will be either Nmap or massscan. You need to learn some basic flags and understand why you might want to use some and not others depending on the scenario. This is usually the first step in any operation.

      For more advanced infrastructure stuff, check out the HackTricks gitbook, it's really helpful.

      For web (not web3) based stuff, you can start with Damn Vulnerable Web App and OWASP Juice Shop. The former is far more tutorialy but the latter has all sorts of walkthroughs. Understanding why this works is important to understanding in future what kinds of stuff work, which is important when people actually put in (bypassable) protections.

      If you want to go through more of a web3 route, get familiar with the Remix IDE and check out Ethernauts.

      For mobiles, it's important to have jailbroken or rooted devices, especially in the case of iOS. Check out Damn I secure and Vulnerable App (Android) or Damn Vulnerable iOS App (iOS)

      Once you get comfortable, you can also check out Capture The Flag challenges hosted by other people. CTFTime is a good aggregate for these and HackTheBox is a good training ground for them.

      I would generally recommend these tools before going onto certs; once you're good at these, you'll breeze through the certs with a light refresher on course details, however the certs are an expensive way to actually learn.

      As for which certs, CompTIA Pentest Plus is a good starter. Offensive Security Certified Practitioner (OSCP) is a good mid-level cert, and CTFs are a crazy good preparation (this exam is much more practical-based than your standard exam). Don't listen to some LinkedIn lunatics that call this a starter exam, it absolutely is not, and they probably have never taken it. It is, however considered something of a gold standard in the industry; if it isn't a minimum requirement, it is considered VERY helpful in most job applications.

      source
    • micka190@lemmy.world ⁨6⁩ ⁨months⁩ ago

      John Hammond’s got some pretty good “getting started with White Hat hacking” videos on his YouTube channel (a lot of “hack a box” and “CTF” style videos). He’s got one or two where he talks about his resume and training/classes he’s done.

      source