Skip to main content
News Directory 3
  • Business
  • Entertainment
  • Health
  • News
  • Sports
  • Tech
  • World
Menu
  • Business
  • Entertainment
  • Health
  • News
  • Sports
  • Tech
  • World
60 Malicious Ruby Gems Downloaded 275,000 Times - Credential Theft - News Directory 3

60 Malicious Ruby Gems Downloaded 275,000 Times – Credential Theft

August 10, 2025 Lisa Park Tech
News Context
At a glance
Original source: bleepingcomputer.com

Malicious ⁣Ruby Gems Steal Credentials, Fingerprint Devices in ⁤Ongoing Supply Chain Attack

Table of Contents

  • Malicious ⁣Ruby Gems Steal Credentials, Fingerprint Devices in ⁤Ongoing Supply Chain Attack
    • How the ⁤Attack Works: A Deep Dive
    • The Persistence of the ⁤Threat
    • Protecting Yourself:‍ Best Practices for Developers

A ⁣recent campaign has compromised RubyGems, the package manager for⁢ the Ruby programming language, with 60 malicious gems designed to steal ⁣sensitive information from developers. Security researchers at Socket discovered the operation, which harvests credentials like plaintext passwords, ⁣device MAC addresses for fingerprinting, and package names for tracking campaign performance.

The ⁣attackers are leveraging supply chain attacks to inject malicious code into seemingly legitimate packages, exploiting developers’ trust in open-source repositories. This⁤ isn’t a new tactic – malicious RubyGems packages have been used in attacks ⁣for several years – but the scale and sophistication of this recent campaign are ‍raising concerns.

How the ⁤Attack Works: A Deep Dive

The malicious gems‍ masquerade⁣ as legitimate tools, often with names similar to popular libraries. Once installed, they silently collect ⁣data from developers’‍ systems. This data⁢ includes:

Plaintext passwords: A ⁤particularly alarming find, indicating the⁤ gems are designed to capture credentials as they are entered.
device MAC Addresses: Used for device⁢ fingerprinting, allowing attackers to uniquely identify and track compromised machines.
Package Names: Collected to monitor the performance and reach of the campaign, helping ⁢attackers understand which targets are most vulnerable.Adding to the deception, some of the tools provide fake success or ⁣failure messages, making it⁢ difficult for developers to immediately detect the compromise. Socket’s inquiry revealed connections to marketingduo[.]co[.]kr, a website flagged as suspicious and linked to the attackers. They’ve also found credential logs on russian-speaking darknet ⁢markets that appear⁣ to originate from these‍ malicious gems.

(Image: Infostealer logs linked to the campaign – Source: Socket)

The Persistence of the ⁤Threat

Despite being discovered,at least 16 of the 60 malicious gems ⁣remain available on RubyGems as of‍ this⁤ writing. ‍The RubyGems team has been notified and⁢ is working to⁤ remove⁣ them, ⁤but the ongoing availability highlights the challenges of securing open-source supply⁢ chains.

This incident follows a similar case reported by Socket in June, where malicious gems were‍ used to target Telegram bot developers by typosquatting the ⁣popular Fastlane automation⁢ tool. These repeated attacks underscore a worrying trend of increasingly sophisticated threats targeting the Ruby ecosystem.

Protecting Yourself:‍ Best Practices for Developers

The best defense against‍ these supply chain attacks is vigilance and proactive security measures. Here’s what developers can ⁢do ‍to protect themselves:

Scrutinize Dependencies: Carefully examine the libraries you’re using, paying close attention to the publisher’s reputation and release history. Look for any signs of suspicious code, such as obfuscation.
Lock Dependencies: Pin your dependencies ‍to specific, known-to-be-safe versions.This prevents unexpected updates from introducing malicious ⁤code. Use a Gemfile.lock to ensure ‍consistent dependency versions across your advancement habitat.
Regularly Audit Your Projects: Periodically review your project’s dependencies⁢ for vulnerabilities and⁢ outdated packages. Tools like bundler-audit ‍ can help automate⁣ this process. Be ‍Wary of Typosquatting: Double-check package names for subtle misspellings that could indicate ⁢a malicious imitation. Implement Robust Security Practices: ⁣Avoid storing sensitive information like passwords in plaintext. Utilize secure credential management solutions and follow secure coding practices.
* Stay Informed: ⁣ keep⁤ up-to-date with the latest security threats and vulnerabilities affecting the Ruby ecosystem.⁢ Follow security blogs and mailing lists to stay informed.Supply chain attacks ‍are a growing threat, ⁣and developers must ⁣prioritize security throughout the software ⁤development lifecycle. By adopting ‍these best practices, you can significantly reduce your risk of falling victim to malicious packages and protect your sensitive data.

Share this:

  • Share on Facebook (Opens in new window) Facebook
  • Share on X (Opens in new window) X

More on this

  • Aaron Sorkin removes Donald Trump references from The Social Reckoning
  • How to Safely Remove Bloatware from Windows Using Built-In Tools

Related

Search:

News Directory 3

News Directory 3 catalogs US newspapers, news services, newsstands and digital news outlets across all 50 states. Browse local publishers by city, state, or topic, and follow current headlines linked back to their original sources.

Quick Links

  • Disclaimer
  • Terms and Conditions
  • About Us
  • Advertising Policy
  • Contact Us
  • Cookie Policy
  • Editorial Guidelines
  • Privacy Policy

Browse by State

  • Alabama
  • Alaska
  • Arizona
  • Arkansas
  • California
  • Colorado

© 2026 News Directory 3. All rights reserved.
For contact, advertising, copyright, issues email: office@newsdirectory3.com