I almost got hacked by a 'job interview'
191–200 of 534 posts
Re: I almost got hacked by a 'job interview'
#192Earlier quoted context omitted.
> Seasoned accounts are a positive heuristic in many domains, not just LinkedIn. Yep. This is how the 3 major credit bureaus is the United States to verify your identity. Your residence history and your presences on the distributed Internet is the HARDES to fake.
sucks to be young I guess.
Re: I almost got hacked by a 'job interview'
#193This article was written by an LLM. I get that the author might be self-conscious about his English writing skills, but I would still much rather read the original prompt that the author put into ChatGPT, instead of the slop that came out. The story - if true - is very interesting of course. Big bummer therefore that the author decided to sloppify it. David, could you share as a response to this comment the original…
* You had the headline spot on. Then you explained what you thought might be the reason for it.
* Then you pondered about why the OP might have done it.
* Finally you challenged the op to all but admitting his sins, by asking him to share the incriminating prompt he used.
---
(my garbage wasn't written by AI, but I tried by best to imitate it's obnoxious style).
Re: I almost got hacked by a 'job interview'
#194I've been hacked a couple of times, all job offers coming from linkedin. Now I calmly refuse to run code as a way to evaluate me and they stop asking. Be polite, say no, move on. * I wish linkedin and github were more proactive on detecting scammers
I've gotten less spam from literally spam testing services than github.
Re: I almost got hacked by a 'job interview'
#195> The scary part? This attack vector is perfect for developers. We download and run code all day long. GitHub repos, npm packages, coding challenges. Most of us don't sandbox every single thing. Embedded into this story about being attacked is (hopefully) a serious lesson for all programmers (not just OP) about pulling down random dependencies/code and just yolo'ing them into their own codebases. How do you know your…
What I'm wondering about is, if you have lots of dependencies, like in the hundreds or thousands, idk how many npm packages usually can have for the average web dev project, how do you even audit all of that manually? Sounds pretty infeasible? This is not to say we should not worry about it, I'm just genuinely curious what do you do in this situation? One could say well don't get that many dependencies to begin with,…
Re: I almost got hacked by a 'job interview'
#196I know Node has the new permissions model thing, but why can’t this be as easy as blocking all fs access above cwd? I’d love a global Node setting for this.
Re: I almost got hacked by a 'job interview'
#197Re: I almost got hacked by a 'job interview'
#198The Setup
The Scoop
The Conclusion
I hate AI slop.
Re: I almost got hacked by a 'job interview'
#199I asked them the same questions I ask all scammers: How was this easier than just doing a normal job? These guys were scheduling people, passing them around, etc. In the grand scheme of things they were basically playing project manager at a decent ability, minus the scamming.
Re: I almost got hacked by a 'job interview'
#200https://github.com/lavamoat/kipuka
It's an upcoming part of the LavaMoat toolkit (that got on main page here recently for blocking the qix malware)