CampaignsFake interview / recruiter lure
Contagious Interview npm 'test assignment' wave delivering OtterCookie (197+ packages)
- Status unknownWe can't confirm whether this has been taken down. Treat it as possibly live. Status checked .
- Moderate confidence
- Indicators (5): CSV, JSON
- Seen to
Do this now
- Block the listed packages in the npm proxy or allowlist
- Alert when node contacts *.vercel.app during npm install
- Run recruiter-supplied projects only in disposable VMs
Indicators to check
Look for any of these on your machines or in your logs:
- package
tailwind-magic - package
react-modal-select
What happened
Fake recruiters sent Web3 developers coding tests whose projects depended on lookalike npm packages. Socket counted 197 new malicious packages from 10 Oct 2025, with more than 31k downloads. The packages fetched a payload from GitHub through Vercel staging apps and installed an OtterCookie build that merges BeaverTail loader functions with stealer and RAT features.
- npm
- GitHub
- Vercel
- Google Docs
- Windows
- macOS
- Linux
Attack chain
-
Lure
LinkedIn recruiter outreach; the assignment arrives in a Google Doc, and the candidate is pressured to run it outside a container while sharing their screen
First seen
-
Artifact
Interview project with a malicious npm dependency (lookalike UI and Tailwind packages)
-
Actor
Contagious Interview, DPRK (attribution: Socket; basis: OtterCookie/BeaverTail code lineage and the shared GitHub-plus-Vercel delivery pattern)
-
Infrastructure
- GitHub account hosting payload repos (removed)
- Vercel staging apps
- C2 on a high TCP port
Last seen
Timeline
- First seen
- Socket reports
- Last seen
- Status checked: Status unknown
Related campaigns
| Type | Value | Copy |
|---|---|---|
| package | tailwind-magic | |
| package | react-modal-select | |
| domain | tetrismic[.]vercel[.]app | |
| domain | knightsbridge-dex[.]vercel[.]app | |
| ip | 144[.]172[.]104[.]117 |
Confidence: Moderate
Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.
Sources
Notes
- The C2 IP was reported on port 5918.
- Socket said 15 packages were still live when it published; their current status was not checked.
Corrections
No corrections.
See the corrections policy. Spotted an error? Tell us.