this post was submitted on 04 Nov 2026
115 points (99.1% liked)

Technology

89588 readers
3075 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
115
Binance says hackers used fake job interview in record crypto heist (www.independent.co.uk)
submitted 5 days ago by new_otters_raft@piefed.ca to c/technology@lemmy.world
7 comments fedilink hide all child comments
 

According to the report, the attack started when an employee from Binance's wallet developer team downloaded an AI tool in June that had been tampered with. The crypto exchange detected the compromise, replaced the device, and changed credentials. But the employee's role, and that of others on the wallet team, was exposed to the hacker. A second software engineer was targeted in September.

The engineer was seeking a new job and downloaded a "malicious code repository" onto his computer after interviewing for what he thought was a legitimate role. The interview process included a virtual meeting with the CEO of a fictitious company.

On October 20, the attacker used the compromised computer plus an internal AI tool to gain control of the wallet developer's system and that of a second wallet developer on that team.

On 29 October, the attacker used the second wallet developer's computer, using stolen credentials from the first wallet developer, and triggered a malicious script to launch the attack.

you are viewing a single comment's thread
view the rest of the comments
[–] sarahreid@lemmy.world 2 points 4 days ago

The June part is what stuck out to me. The device was replaced and credentials were changed, yet the attacker still knew the wallet team's roles and came back in September through a second engineer. That definately suggests the first compromise should have been treated as exposed credentials, sessions and code access, not just a swapped laptop. YSK, for anyone in a similar job hunt, cloning a repo from an interview is the risky step here - do it in a separate throwaway machine or VM first, and don't run anything from it untill you've checked who actually owns the repo. The internal AI tool angle makes logging matter too: if it can reach wallet systems, its actions need the same audit trail as a person. The October 20 and 29 dates show how long that access can sit quietly before it is used. Hope that helps.