Somewhere right now, a software developer is opening a repository they were sent as part of a job interview. If the people behind the campaign researchers are calling PolinRider had their way, that single act, just opening the folder, would be enough to hand over their credentials, their browser secrets, and a foothold on their machine.

The raw numbers are striking on their own. North Korea-linked actors tied to the long-running Contagious Interview operation published 108 malicious packages and browser extensions across npm, Packagist, Go, and Chrome, reported by The Hacker News with technical analysis from JFrog and Socket. Some impersonate legitimate projects so closely, down to the description and repository metadata, that a quick glance would not catch them. But the scale is not really the story. The delivery is.

There are three moving parts, and none of them is the tired "install a bad package and get infected." First, the impersonation, betting on a typo or a rushed dependency add. Second, and more clever, the packages hide loaders that fetch their real payload not from a server an authority can seize, but from public blockchain infrastructure, which has no single domain to take down. And third, the part that should make every engineer uneasy: in a related cluster the attackers plant Visual Studio Code task files set to run the moment a folder is opened. No install, no run button. You open the project in VS Code or Cursor, and the code executes.

Put those together and you understand why this actor has spent well over a year targeting developers specifically, usually through fake job interviews where the candidate is asked to complete a coding assignment. It preys on the one moment a careful engineer lowers their guard, a job opportunity, and pairs it with a trick that turns "just looking at the code" into "running the code." As of April 2026 the broader campaign had reached 1,951 GitHub repositories across more than a thousand owners.

The reason this lands harder than an ordinary supply-chain story is what a developer's laptop now holds: cloud keys, source code, and the CI access that touches everything downstream. Two shifts make it worse. AI coding assistants that ingest or auto-run untrusted repositories widen the blast radius of the folder-open trick, and a blockchain-based payload channel defeats the usual takedown playbook. The uncomfortable conclusion is that you can no longer trust a package because it looks right, and you can no longer assume your editor is a passive reader.

The practical defenses are unglamorous but real. Never open an untrusted repo, and especially not an interview assignment, in your main environment; use a disposable VM or container. Disable automatic task execution in VS Code and Cursor, and read the .vscode/tasks.json before you open anything unfamiliar. Pin and lock dependencies, scan for the named packages, and rotate secrets on any machine that touched them. And treat a recruiter's coding test that requires you to run code as hostile until proven otherwise.

Sources: The Hacker News, The Hacker News on the Rollup polyfill packages, with research from JFrog and Socket.