A new wave of supply chain attacks is spreading across the open source world, and this time the target is developers themselves. <\/p>\n
Security researchers have uncovered a campaign called PolinRider that hides malicious JavaScript loaders inside trusted code repositories, waiting for unsuspecting developers to run them.<\/a><\/p>\n The campaign has been linked to North Korean threat actors tied to the broader Contagious Interview and Famous Chollima activity clusters. <\/p>\n These groups are known for targeting software engineers with fake job offers<\/a> and infected coding tests, and PolinRider appears to be an extension of that playbook, only this time hidden inside legitimate looking packages.<\/a><\/p>\n What makes PolinRider dangerous is its reach. It began on npm but has since spread into Packagist, Go modules, and even a Chrome extension, showing the attackers are not sticking to a single ecosystem.<\/a><\/p>\n Researchers from Socket.dev said the campaign has grown far larger than earlier reports suggested. <\/p>\n Socket.dev said in a report<\/a> shared with Cyber Security News (CSN) that they identified 162 malicious release artifacts spread across 108 unique packages and extensions, including 80 compromised Go modules, 10 Packagist packages, and one Chrome extension.<\/a><\/p>\n The scale of this discovery shows how a single group can quietly poison multiple corners of the open source supply chain at once. Because the malicious code hides inside legitimate looking files, many developers may have installed it without realizing anything was wrong.<\/a><\/p>\n The attackers behind PolinRider rely on a mix of old and new tricks to stay hidden. Earlier waves buried obfuscated JavaScript inside configuration files such as those ending in config.js, counting on developers not to scroll through every line of code.<\/a><\/p>\n More recent versions disguise the malicious script as a fake dot woff2 font file<\/a>, a format most developers would never think to inspect. <\/p>\n Execution is triggered quietly through Visual Studio Code task files, which can run automatically when a folder is opened.<\/p>\n Once active, the loader reaches out to blockchain and public RPC services, including TRON, Aptos, and BNB Smart Chain networks. <\/p>\n It uses these connections to fetch an encrypted second stage payload, decrypt it with an embedded XOR key, and run it using the eval function.<\/a><\/p>\n The payloads observed so far include DEV#POPPER and OmniStealer, both capable of remote command execution, communicating with attacker servers through socket.io-client, and stealing credentials, browser data, and wallet information.<\/a><\/p>\n A major piece of this campaign centers on a GitHub account named Xpos587. Several repositories tied to this account were modified within the same narrow window on June 23 at 10:00 UTC, a pattern that lines up with account takeover rather than normal maintenance.<\/a><\/p>\n Two repositories connected to this account, Xpos587\/git2md and Xpos587\/markfetch, along with a separate project called Artiffusion-Inc\/mirofish, were found carrying the hidden loader. <\/p>\n The markfetch repository used the fake font trick, while mirofish hid its payload inside a file called vite.config.js. <\/p>\n On Packagist, the campaign expanded through a namespace called sevenspan, tied to the 7span organization, with the 7span\/react-list package among those affected. <\/p>\n Maintainers removed the fake font files once discovered, but obfuscated code hidden in configuration files remained untouched<\/a>, showing partial cleanup is not enough.<\/a><\/p>\n The attackers also used Git history rewriting, including force pushes and backdated commits, so tampered code appears older than it really is. <\/p>\n Visible commit history on GitHub cannot be trusted alone, and defenders need to check activity logs directly.<\/a><\/p>\n Security teams should treat any environment running an affected package as compromised until proven otherwise. <\/p>\n The company recommended preserving forensic evidence, rebuilding from known good lockfiles, and rotating exposed secrets from a clean machine rather than the infected one.<\/a><\/p>\n Additional guidance includes auditing machines for VS Code tasks<\/a> set to run automatically on folder open, and reviewing repositories for suspicious changes to files like tasks.json, config.js, and vite.config.js.<\/a><\/p>\n Indicators of Compromise (IoCs):-<\/strong><\/p>\nNorth Korea-Linked Hackers Hide JavaScript Loaders<\/strong><\/h2>\n
![\"The](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEhc1YJzB9JEMI8DeVyWMC1TqicgFWFB1AmT9iE9yZ4Ko8bH4DnD_6Kuxe1BcM-HxCGBwIPYnUNd0S0lEf5vzkc1LJwUVVCP-ro2j5s6ReNc1xMQkU5dFw_v8c8hSeZyFALOCed0gj9tztf0PKTbyhvmTkCDPPlBMWaV8yq_lgIPYYxIETwzavwFpyU29-4\/s1600\/The%2520Xpos587%2520repository%2520list%2520shows%2520multiple%2520unrelated%2520projects%2520updated%2520in%2520the%2520same%2520period%2520%28Source%2520-%2520Socket.dev%29.webp?ssl=1\")
Compromised Accounts and Repository Manipulation<\/strong><\/h2>\n
![\"GitHub](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEhQu5YWtHzhYdyZvoj-cTtJHS37f4Iblu9nk9yAIUEJNh0IVhrIsXTGVZz5ViNPw3RASn6haQfBOSecJoRcyTEfErWCbOXJ7ECZO7Eg0puRqL914HR3dypbP0f0dikQvcNN5Z99nmYGhkbI-htDcpu8wIB2FxXPHqekCvHMIwBc5q-IV2EMjS5blRWCQhU\/s1600\/GitHub%2520Activity%2520exposes%2520the%2520force%2520push%2520used%2520to%2520rewrite%2520repository%2520history%2520%28Source%2520-%2520Socket.dev%29.webp?ssl=1\")