Cybersecurity researchers have discovered a number of malicious packages in the NPM registry specifically targeting a number of prominent media, logistics, and industrial firms based in Germany to carry out supply chain attacks.
“Compared with most malware found in the NPM repository, this payload seems particularly dangerous: a highly-sophisticated, obfuscated piece of malware that acts as a backdoor and allows the attacker to take total control over the infected machine,” researchers from JFrog said in a new report.
The DevOps company said that evidence points to it being either the work of a sophisticated threat actor or a “very aggressive” penetration test.
All the rogue packages, most of which have since been removed from the repository, have been traced to four “maintainers” – bertelsmannnpm, boschnodemodules, stihlnodemodules, and dbschenkernpm — indicating an attempt to impersonate legitimate firms like Bertelsmann, Bosch, Stihl, and DB Schenker.
Some of the package names are said to be very specific, raising the possibility that the adversary managed to identify the libraries hosted in the companies’ internal repositories with the goal of staging a dependency confusion attack.
The findings build on a report from Snyk late last month that detailed one of the offending packages, “gxm-reference-web-auth-server,” noting that the malware is targeting an unknown company that has the same package in their private registry.
“The attacker(s) likely had information about the existence of such a package in the company’s private registry,” the Snyk security research team said.
ReversingLabs, which independently corroborated the hacks, said that the rogue modules uploaded to NPM featured elevated version numbers than their private counterparts to force the modules onto target environments — a clear indicator of a dependency confusion attack.
“The targeted private packages for the transportation and logistics firm had versions 0.5.69 and 4.0.48, while the malicious, public versions were identically named, but used versions 0.5.70 and 4.0.49,” the cybersecurity firm explained.
“The attack is highly targeted and relies on difficult-to-get insider information,” the researchers said. But on the other hand, “the usernames created in the NPM registry did not try to hide the targeted company.” Read more: https://bit.ly/3L4Rv11
You can also read this: Over 200 Malicious NPM Packages Caught Targeting Azure Developers