Beware of Fake Coding Interviews: How Crypto Wallet Scammers Target Developers

Fake coding interviews are a scam where a bogus recruiter sends a "technical assignment" whose real purpose is to get you to connect a crypto wallet and sign a message. The signature — not the code you write — is the payload. It can authorise transfers or token approvals that drain the wallet afterwards.

TL;DR: a legitimate interview never asks you to connect a real wallet. If an assignment involves signing anything, use a burner wallet with zero funds, or walk away.

Over the past few months, I’ve noticed a new wave of scams targeting developers, especially those searching for remote jobs. I recently encountered two myself — and I want to share it here so that others don’t fall into the same trap.

The Setup#

It starts the way most recruitment messages do:

“Our CTO was really impressed with your experience. We’d like to move forward with a short skills test before arranging the technical interview.”

So far, so normal. But then came the task:

• Clone a GitHub repo.
• Replace the existing MetaMask wallet integration with Coinbase or another Ethereum wallet.
• Connect your wallet and sign the message “Connected successfully” and show the signed hash in the browser console.
• Share a screenshot or short video as proof.

And after that? They give amazing promises..

Why the signing step is the whole scam#

Read the task list again and notice what is missing: nothing in it evaluates your engineering ability. Swapping one wallet connector for another is boilerplate. The only step that carries any weight is the signature — and that is the point.

Wallet signature prompts are notoriously hard to read. A request may display as harmless text while actually authorising a token spending allowance or a transfer. The friendly string "Connected successfully" exists to make the prompt look routine, so you approve it without scrutinising what your wallet is really being asked to consent to.

The proof-of-work framing does double duty. Asking for a screenshot or video makes the request feel like normal interview diligence, while confirming to the scammer that a real wallet with a real balance completed the flow.

There is a second risk even if you never sign. Cloning and running an unfamiliar repo executes its install scripts on your machine. Postinstall hooks and obfuscated dependencies are a well-documented vector for stealing browser profiles, SSH keys, and environment files — so the damage does not require you to reach the signing step at all.

Red Flags to Watch Out For#

• Unprofessional communication. Contact from a personal Gmail rather than a company domain, a chat moving to Telegram immediately, or messages with inconsistent names and job titles.
• Random public repos. A brand-new repository with almost no commit history, no contributors, and no issues. Real take-home assignments come from an established company template.
• Wallet involvement. The decisive one. No legitimate hiring process needs access to your personal funds to assess your skills.
• Urgency + flattery. Heavy praise paired with a tight deadline is engineered to stop you pausing long enough to check anything.
• No interview before the task. Being handed a technical assignment before any human conversation inverts the normal order of a hiring process.

How to Protect Yourself#

• Never use your real wallet for any coding assignment. If you absolutely must, set up a burner wallet with no funds.
• Inspect the repo carefully before running it. Look for hidden approval or transaction calls.
• Run unknown code in a container or VM, never directly on the machine holding your keys and credentials.
• Research the company. Check their website, LinkedIn presence, and whether employees actually exist. (sometimes they pretend they are from some well know company but they are not belong to it)
• Verify through a separate channel. Find the company's real site yourself and contact a listed employee — never through a link the recruiter supplied.
• Trust your gut. If something feels off, it probably is.

What to do if you already signed#

Act on the assumption that the wallet is compromised, and move quickly:

1. Move your assets first. Transfer funds and NFTs to a wallet whose seed phrase has never touched the affected machine or browser.
2. Revoke token approvals using a reputable approval-checker tool. A signature granting spending allowance stays valid until it is explicitly revoked.
3. Stop reusing that wallet. Retire it rather than trying to clean it up.
4. Assume the machine is suspect if you ran the repository. Rotate SSH keys, API tokens, and any credentials stored in .env files.

Frequently asked questions#

Is signing a message really dangerous if no transaction is sent?#

It can be. Certain signature types grant permissions rather than transferring anything immediately — the transfer happens later, using the authorisation you already gave. No on-chain transaction at signing time does not mean no risk.

Do legitimate Web3 companies ever ask for a wallet in interviews?#

They may ask you to work with wallets on a testnet, using test funds with no real value. A request involving mainnet or your personal wallet is not a normal hiring practice.

The recruiter had a real LinkedIn profile. Doesn't that verify them?#

No. Profiles are cheap to fabricate and real employees are routinely impersonated. Verify by contacting the company through details you found independently, not through anything the recruiter sent you.

Final Thoughts#

These scams are clever because they play on a developer’s eagerness to land a job. By disguising themselves as interview assignments, scammers hope to lure skilled professionals into exposing their wallets.

Remember:

A coding interview should test your brain, not your bank balance.

On the other side of the table, here is how I approach hiring developers and technical assignments — what a real process looks like.