Friday, December 27, 2024
HomeCyber Security NewsNascent Malware Attacking npm, PyPI, and RubyGems Developers

Nascent Malware Attacking npm, PyPI, and RubyGems Developers

Published on

SIEM as a Service

Phylum analyzes source code and metadata for all registry-pushed packages. This year, in millions of packages they are aiming to examine nearly a billion files, as this will enable them to get unique insights into package behaviors across ecosystems.

That’s why it has been actively tracking various recent malware campaigns, from fake npm package updates to GCC binary impostors and complex data exfiltration setups.

Besides this, the cybersecurity analysts at Phylum recently reported about Nascent malware attacking developers of the following platforms and programs:-

- Advertisement - SIEM as a Service

Nascent Malware on Registry packages

Phylum’s automated platform alerted researchers about the “kwxiaodian” package on September 3, 2023, and in its setup.py the following contents were revealed:-

Contents of setup.py (Source – Phylum)

Simultaneously, they received alerts about harmful npm packages executing specific actions in the package.json preinstall hook, and then the obfuscated index.js file was executed.

Here below, we have mentioned all the things that this package does:-

  • The network interface info is gathered initially.
  • Basic information like OS details, free memory available, etc., were also collected.
  • If the platform is not macOS, then the execution is automatically terminated.
  • Lastly, it encrypts and sends data to the attacker’s server.

The Rubygems package mirrors PyPI and npm patterns, triggering automatic execution via the “Rakefile” to collect and send host information to a remote server.

Ruby platform data collection (Source – Phylum)

Ecosystems Commonalities 

However, apart from all these things, the campaigns targeting npm, PyPI, and RubyGems are identical, as revealed by the researchers upon close review analysis.

Here below, we have mentioned all the commonalities:-

  • On 81.70.191.194, all the packages communicate with a service.
  • Collects and sends system info to this service.
  • On macOS systems, the packages execute only.
  • Similar versions across ecosystems were published.

Timeline

Full package timeline (Source – Phylum)

Malware is widespread in open-source registries, and despite security awareness, developers often pull and execute packages from unknown sources. Making manual audits impractical due to the increasing number of dependencies.

In this scenario, using automated solutions to detect and block packages violating defined policies is a wise approach to managing malware and other risks.

Keep informed about the latest Cyber Security News by following us on Google News, Linkedin, Twitter, and Facebook.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...

Palo Alto Networks Vulnerability Puts Firewalls at Risk of DoS Attacks

A critical vulnerability, CVE-2024-3393, has been identified in the DNS Security feature of Palo...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Lumma Stealer Attacking Users To Steal Login Credentials From Browsers

Researchers observed Lumma Stealer activity across multiple online samples, including PowerShell scripts and a...

New ‘OtterCookie’ Malware Attacking Software Developers Via Fake Job Offers

Palo Alto Networks reported the Contagious Interview campaign in November 2023, a financially motivated...

NjRat 2.3D Pro Edition Shared on GitHub: A Growing Cybersecurity Concern

The recent discovery of the NjRat 2.3D Professional Edition on GitHub has raised alarms...