StepSecurity published new findings on November 13, 2026 about AccuraSoftHire, a fake hiring company that hands job candidates a coding test loaded with malware. Its analysis shows that two of the npm packages used in that test could be installed for roughly five and seven months until npm swapped them out on November 12 and November 13.
The work builds on JFrog research from November 9 that first exposed the fake company. It matters to every team that lets developers run outside code on a work laptop, because one infected machine can hand over the keys to source code and cloud accounts.
How the Fake Interview Works
According to the JFrog research that StepSecurity summarizes, AccuraSoftHire looked like a real employer. It had a careers site with open roles, job ads on well-known boards, recruiters whose LinkedIn profiles carried verification badges, and a GitHub account for its project manager.
Candidates were pushed to run the attacker's code in three ways:
- Take-home test: a React landing page task with eleven plugins in its Tailwind CSS setup. Ten of them are genuine, and one is a copy of an official plugin with a malware loader appended to the file.
- Camera driver: the video check always fails until the candidate runs a one-line curl command that downloads a so-called driver.
- Browser extension: candidates are told to load an unpacked Chrome extension out of a job-new-alerts folder, followed by a PowerShell script.
The loader in the test does not run during npm install. It fires once Tailwind compiles the stylesheet, and compiling is step one of the assignment.
What StepSecurity Added
On November 13, StepSecurity looked up each package JFrog had named in the npm registry. None of the ten is available any more: one was unpublished and the others were swapped for npm's security placeholder. The publish records show how unevenly that happened.
- tailwind-lines-clamps: published April 16, replaced November 13, 211 days online, 2,326 downloads in 2026.
- tailwind-lineclamp: published May 27, replaced November 12, 169 days online, 2,060 downloads.
- tailwind-forms-kit: 36 days online and 1,002 downloads.
- Most others: removed after one to 23 days.
StepSecurity notes that the download numbers include mirrors and security scanners, so real installs are lower. It also says it does not know why some packages lasted months while others disappeared within days.
A Server Address Hidden in Ethereum Transactions
The loader carries no server address of its own. It reads the latest transaction sent from one Ethereum wallet and decodes the address from the recipient field. To switch servers, the attacker only sends a new transaction, and no package has to change.
Because the blockchain is public, StepSecurity decoded the wallet's whole history: 609 outgoing transactions, beginning July 25. Together they reveal eight server addresses, the newest dated October 19. The StepSecurity post lists them all in its indicator table.
The careers site itself no longer resolves. StepSecurity warns that this does not end the operation, because the same kind of loader also appeared in hijacked versions of established npm packages in early November.
What It Means for Developers
Three common defenses fail here. Turning off npm install scripts does not help, because the malicious code waits for the build. An IP block list taken from a single sample is outdated the moment the wallet announces another server.
The added code is also hard to spot. It is tacked onto the bottom of a genuine plugin file, often after enough blank space to hide it from view in an editor.
The seven-month package is the main lesson. A cooldown that holds back freshly published versions, like the dependency cooldowns Cargo gained in Rust 1.100, would have stopped the short-lived copies but not the two that stayed for months. For those, you need to know what is installed on each developer machine.
The stolen data is the same kind seen in other recent attacks on developers, such as the wfx-loot CI secret stealer campaign. Researchers cited by StepSecurity report that the malware takes browser, SSH, cloud and git credentials, then uses git access to plant the loader in the victim's other repositories.
What to Check Now
- Packages: search node_modules folders for the ten names on the indicator list, including tailwind-lines-clamps, tailwind-lineclamp, tailwind-forms-kit and tailwind-custom-forms. Removed packages still run from local copies on each build.
- Editor files: look for .vscode/tasks.json entries set to run when a folder opens. In VS Code, switch off automatic tasks and keep Workspace Trust on.
- Browsers: look for an unpacked extension loaded from a job-new-alerts folder.
- Network logs: search for the eight server addresses and for plain HTTP traffic on port 443 to a bare IP address.
- Policy: keep interview assignments, drivers and recruiter setup commands off company machines. Use a throwaway virtual machine with no tokens or keys.
When a machine turns out to be infected, change all credentials kept on it and inspect the repositories it could push to. Wiping the laptop alone may not be enough, since the loader can already be in code the developer will open again.
Conclusion
The AccuraSoftHire packages are off npm, but copies remain wherever they were installed, and the same loader is spreading by other routes. Check developer machines against the published indicators and treat any take-home test from a stranger as untrusted code.
Sources
- StepSecurity: Inside the AccuraSoftHire Fake Interview Campaign
- JFrog Security Research: Contagious Interview - One Interview Away From Infection
See my articles more often when you search Google.
