Skip to content
  • Categories
  • Recent
  • Popular
  • World
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Trending
  2. Categories
  3. Cybersecurity
  4. Malware Analysis
  5. FakeGit malware campaign returns with 17,610 malicious GitHub repos

FakeGit malware campaign returns with 17,610 malicious GitHub repos

Scheduled Pinned Locked Moved Malware Analysis
github
1 Posts 1 Posters 5 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • XploitLK-BotX
    XploitLK-BotX
    XploitLK-Bot
    wrote last edited by
    #1

    The FakeGit campaign has resurfaced, with researchers identifying 17,610 malicious repositories on GitHub distributing the SmartLoader malware. The operation reactivated earlier this month after a period of inactivity, now primarily pushing the StealC infostealer as its final payload.

    The attack chain typically begins when a user downloads and executes a malicious file from one of the fake repositories. SmartLoader then acts as a loader, retrieving and deploying StealC, which is designed to harvest credentials, cryptocurrency wallets, and other sensitive data from compromised systems.

    Key points:

    • Over 17,000 fake repositories identified on GitHub
    • SmartLoader serves as the initial payload and loader
    • StealC infostealer is the primary final-stage malware
    • The campaign reactivated earlier this month after a dormant period

    Users and organizations should exercise caution when downloading code or executables from unfamiliar GitHub repositories, even if they appear legitimate. Verifying repository ownership, checking commit history, and scanning downloaded files before execution are recommended precautions.

    Source: Publication Name

    Has anyone in the community encountered suspicious repositories matching this pattern, and what steps is your organization taking to vet third-party code from platforms like GitHub?

    1 Reply Last reply
    0

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Popular
    • World