• Socsa@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    26
    ·
    3 years ago

    Honestly I can see this being the worlk of someone who had to deal with one of those stupid fucking online interview code tests which require crazy screen monitoring permissions. What a better way to kill off that trend entirely than to make the very practice an active cyber-security risk?

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 years ago

      My company has a strict policy against take home coding challenges. If we want to see you code, we’ll do the challenge live, open book (just tell us what you’re looking up).

      Bad candidates cheat on those tests, and good candidates don’t have the patience, so they’re worthless. If you’re applying for a job and they have a take home coding challenge, your time is probably better spent elsewhere.

  • circuscritic@lemmy.ca
    link
    fedilink
    English
    arrow-up
    5
    ·
    3 years ago

    They don’t say who was targeted, but I bet this is a backdoor way to infiltrate specific projects. So if they have a list of 163 projects they see a benefit in gaining some sort of access to, they then compile a target list from the relevant developers/contributors to all of those projects, and go from there.

    This isn’t the type of campaign that can be spammed to anyone and everyone both due to logistics and to minimize exposure of the tools being used.