1-minute read of a 4 min report

AccuraSoftHire Interview Test Kept Poisoned npm Packages Available for Months

By

1-minute read

What a defender needs to know

AccuraSoftHire’s fake interview test put a malicious Tailwind look-alike in a React project. StepSecurity’s investigation says the loader runs when the candidate builds CSS, rather than at npm install. The same hiring front promoted a camera “driver” and an unpacked job-alerts extension; a tested extension path ended with an empty program.

The npm record for tailwind-lines-clamps retains an April 16 original version timestamp and a November 13 security replacement. The record for tailwind-lineclamp runs from May 27 to November 12. StepSecurity calculates 211 and 169 days of availability. Its 2,326 and 2,060 download counts include scanners and mirrors. A short package-age cooldown could admit these older names, and a local node_modules copy can still execute in a build.

Search developer machines and project folders for both package names, and inspect .vscode/tasks.json for runOn set to folderOpen. Look for the native messaging helper com.accurasoft.jobalerts and review outbound connections to 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. Move outside interview assignments onto an isolated VM without company credentials; set VS Code task.allowAutomaticTasks to off on managed machines. For a matching machine, isolate it, rotate its stored credentials and inspect repositories the developer could push to. Verify the cleaned project tree and observe a controlled build’s outbound destinations before restoring access.

Primary sources