AccuraSoftHire Interview Test Kept Poisoned npm Packages Available for Months
A fake coding assignment loads a look-alike Tailwind plugin at build time. Check developer project folders and credentials, including packages that outlived a new-package cooldown.

A fake interview assignment led developers toward npm packages that remained available for months. StepSecurity’s November 13 investigation traces the AccuraSoftHire hiring front and its take-home React test: a look-alike Tailwind plugin loads malicious code when the candidate builds the project. If a candidate runs the test on a work laptop, repository and cloud credentials on that machine are exposed.
Two packages named in that research were published in April and May and replaced with security placeholders only in November. A package-age policy that holds new versions for only a few days can admit those older poisoned packages. StepSecurity counted 2,326 downloads of tailwind-lines-clamps and 2,060 of tailwind-lineclamp between January 1 and November 13; those are registry downloads, including scanners and mirrors, rather than a count of infected machines.
A coding test runs the loader
The test asks a candidate to finish a React landing page. StepSecurity, drawing on JFrog’s campaign investigation, describes eleven Tailwind plugins in one version of the project: ten real plugins and one look-alike, tailwind-custom-forms, with a loader appended to an otherwise ordinary plugin file. Its key timing detail is that the loader “does not run during npm install.” It executes when Tailwind builds the CSS, the first step the task requests. An install-script check alone therefore misses this route.
The hiring site accurasofthire[.]com offered a camera-check “driver” after a staged verification failure and instructions for an unpacked job-alerts browser extension. StepSecurity says the Windows driver installer fetched and ran a JavaScript payload; the extension path registered a Chrome and Edge native messaging helper named com.accurasoft.jobalerts. In JFrog’s test the extension’s final program was empty. Treat an installed extension or helper as a reason to investigate the machine, rather than evidence that this particular path delivered malware.
The loader reads its current server address from a public Ethereum wallet, then retrieves further stages over plain HTTP on port 443. StepSecurity decoded the wallet’s transaction history into eight server addresses; changing the wallet transaction can change the destination without changing the installed npm package. A single blocked IP therefore ages faster than the package copy in a project folder.
Old packages defeat a short cooldown
The npm registry entry for tailwind-lines-clamps retains an April 16 timestamp for its historical 0.4.5 version and records a 0.0.1-security replacement on November 13. The registry entry for tailwind-lineclamp records May 27 and November 12 for the same milestones. StepSecurity’s elapsed-time calculation puts those availability windows at 211 and 169 days. The current registry entries expose security placeholders as their latest versions; a developer’s existing node_modules can still hold the earlier code, and building that local project can run it again.
StepSecurity also identified shorter-lived look-alikes: tailwind-custom-forms, tailwindcss-contact-forms, tailwind-form-styles, tailwind-forms-kit, tailwind-clamps-line, scrollbar-hide-plugin, tailwindcss-anim and tailwind-anim. Search package inventories and local project trees for these names as well as the two long-lived packages. Inspect the installed files and project history before cleaning a match; a security placeholder in today’s registry is a different state from an older cached package on a workstation.
The source’s wallet analysis names these server IPs, newest first: 103[.]179[.]142[.]155, 23[.]27[.]13[.]72, 91[.]218[.]183[.]174, 166[.]88[.]134[.]75, 193[.]247[.]144[.]38, 166[.]88[.]73[.]46, 23[.]27[.]13[.]135 and 166[.]88[.]134[.]62. Hunt for connections to those addresses in developer endpoint and network logs. The wallet’s address is 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a; inspect its later transactions when refreshing the network hunt. Also search for requests bearing Sec-V or the paths /0x/cls and /0x/ls, and for auto-run VS Code tasks in .vscode/tasks.json with the separate key runOn set to folderOpen.
Keep interview work off company laptops
Keep outside coding assignments and recruiter-supplied setup software on an isolated personal or disposable VM with no company tokens, SSH keys, wallet data or browser profile. On managed developer machines, turn task.allowAutomaticTasks to off in VS Code, retain Workspace Trust, and open unfamiliar folders in Restricted Mode. Check that policy on a test machine before handing engineers an unfamiliar repository; package age rules remain useful against quick-turnover malware, but the two long-lived packages show why they cannot replace endpoint inventory.
If a machine contains a campaign package or shows a matching connection, isolate it, inventory the credentials stored on it, rotate those credentials and inspect repositories the developer could push to for added loader code. StepSecurity warns that the loader can spread through repositories while preserving commit dates; review file contents and changes across branches rather than relying only on the apparent age of a commit. Then repeat the package, task and network checks on the rebuilt workstation before giving it back its credentials. The decisive test is whether the project tree is clean and a controlled build stays within the expected network destinations.