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. WeaselBiscuit Stealer Spreads via 13 npm Packages to Harvest Chrome Extension Storage

WeaselBiscuit Stealer Spreads via 13 npm Packages to Harvest Chrome Extension Storage

Scheduled Pinned Locked Moved Malware Analysis
chromenpm
1 Posts 1 Posters 12 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 on last edited by
    #1

    Cybersecurity researchers have uncovered a cluster of 13 npm packages being used to distribute a previously undocumented JavaScript stealer tracked as WeaselBiscuit.

    According to OpenSourceMalware, the new malware family shows functional overlaps with two strains tied to the DPRK-linked Contagious Interview campaign: BeaverTail and additional tooling from that operation. The stealer's primary objective is harvesting data stored in Chrome extension storage, a target that can expose sensitive tokens and session data held by browser extensions.

    Key points:

    • 13 npm packages identified as part of the distribution cluster
    • Payload is a JavaScript stealer named WeaselBiscuit
    • The malware is previously undocumented
    • Functional overlap observed with BeaverTail and another strain linked to Contagious Interview
    • Contagious Interview is attributed to the DPRK
    • Targeting focuses on Chrome extension storage

    The overlap with known Contagious Interview tooling is notable, as it suggests either shared tooling, reused code, or an evolution of the campaign's arsenal rather than a fully independent operation.

    If you maintain JavaScript or Node.js projects, review your dependency trees for unexpected or recently added packages, and treat extension storage data as sensitive material worth protecting.

    Source: The Hacker News

    Has anyone seen these npm packages in their own dependency audits, and how is your team handling third-party package vetting?

    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