Live data from Hacker News

I almost got hacked by a 'job interview'

blog.daviddodda.com

411–420 of 534 posts

Re: I almost got hacked by a 'job interview'

#412

Earlier quoted context omitted.

I'm regularly asked by coworkers why I don't run my writing through AI tools to clean it up and instead spend a time iterating over it, re-reading, perhaps with a basic spell checker and maybe grammar check. That's because, from what I've seen to date, it'd take away my voice. And my voice -- the style in which I write -- is my value. It's the same as with art... Yes, AI tools can produce passable art, but it feels s…

I consider myself to be an above average writer and a great editor. I will just throw my random thoughts about something that happened at work, ask ChatGPT to keep digging deeper in my question, I will give it my opinion of what I should do. Ask it to give me the “devil’s advocate” and the “steel man opinion” and then ask it to write a blog post [1]. I then edit it for tone, get rid of some of the obvious AI tells. M…

I dont buy it can tell if something sounds ai. Multiple times i have given it direct ai slop writing and it could not tell it was ai written. As a matter of fact, it would insist it wasnt.

This flow sounds like what an intern did in pr reviews and it made me want to throw something out a window. Please just use your own words. They are good words and much better words than you may think.

Re: I almost got hacked by a 'job interview'

#413

This article is so interesting, but I can’t shake the feeling it was written by AI. The writing style has that feel for me. Maybe that shouldn’t bother me? Like, maybe the author would never have had time to write this otherwise, and I would never have learned about his experience. But I can't help wishing he'd just written about it himself. Maybe that's unreasonable--I shouldn't expect people to do extra work for fr…

that was the case. you can find the base write up and the prompt used in one of my comments on this post. i did not have much time to work on this at all, being in the middle of a product launch at my work, and a bunch of other 'life' stuff. thanks for understanding.

You have good words. Have faith in your words. They are better words than ai even if they few or many. They let us get to know “you”. Ai erases “you”

Re: I almost got hacked by a 'job interview'

#414

Earlier quoted context omitted.

But where does it stop ? Will there be trap clauses in the NDA and contract to see if they carefully read every line ? Will they be left with no onboarding on day one to see how far they can go by themselves ? etc. You're starting the relationship on the base of distrust, and they don't know you, they have no idea how far you're willing to go, and assuming the worst would be the safest option.

We can't have green M&Ms for a reason.

That was an innocent canary clause (they were not asking to put the POS on fire)

The equivalent here would be to ask the candidate to have some folded paper showing his name on camera for the interview, not threatening them with malware.

Re: I almost got hacked by a 'job interview'

#415

The same situation has happened to me multiple times now. I know HN hates blockchain-anything but the attack is mostly aimed at those in that industry and the idea is (1) To try steal cryptocurrencies (2) To try to get inside access to blockchain companies. For my most recent experience it was someone who had forked a "web3" trading app and they were looking for an engineer for it. But when I Googled this project the…

Something like this recently happened to me:

1) Generic company name

2) They asked me to sign an NDA first (this for some reason almost meant trust)

3) The name of the person there had thousands of LinkedIn profiles (a common name)

4) The frontend looked pretty sane, then I had to run truffle migrate

I wonder what's the worst that could happen to me in this scenario.

Thankfully I don't do online banking from the machine and don't have bitcoin wallets.

Re: I almost got hacked by a 'job interview'

#416

> sandbox everything. Docker containers Docker is not a sandbox. How many times does this needs to be repeated? If you are lazy, I would highly suggest to use incus for spinning up headless VMs in a matter of seconds

Perhaps the reason people keep repeating it is that someone makes the statement without any reasons, provides an alternative again without any reasons.

"Why are you not using docker to sandbox your code?"

"Umm.. someone on HN told me docker is not a sandbox, to use randomtool instead"

Re: I almost got hacked by a 'job interview'

#417

Earlier quoted context omitted.

IMO the "better" attack here is to just kind of use Return Oriented Programming (ROP) to build the nefarious string. I'm not going to do the example with the real thing, for the example let's assume the malicious string is "foobar". You create a list of strings that contain the information somewhere: const dictionary = ["barcode", "moon", "fart"]; const payload = [ [2, 0, 1], [1, 1, 2], [0, 0, 3] ];

Very interesting idea. You could even take it a step farther and include multiple layers of string mixing. Though i imagine after a certain point the obfuscation to suspicion ratio shifts firmly in the direction of suspicion. I wonder what the sweet spot is there

Based on the complete out of my behind number I'd say something like 99.9999% of successful hacks I read about use one level of abstraction or less. Heavy emphasis on the less.

So I think one layer of abstraction will get you pretty far with most targets.

Re: I almost got hacked by a 'job interview'

#418

Unfortunatelly I wasn't as lucky to do my due diligence checking the harm on the code before I ran it. I only lost a few dollars I had in my wallet though. This is the code base provided (I already flagged with gitlab): https://gitlab.com/0xstake-group And the actual task (which was a distraction - also flagged with notion): https://www.notion.so/Web3-Project-Evaluation-1f25d6f4dcf180...

It's not down to luck. If you maintain good habits and personal processes you will not fall for this. "Everybody gets phished" is overstated.
Post reply on HN