Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
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 (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. #GitHub was compromised again… via a poisoned #VSCode extension.

#GitHub was compromised again… via a poisoned #VSCode extension.

Scheduled Pinned Locked Moved Uncategorized
githubvscode
3 Posts 2 Posters 0 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.
  • ghostwriter@phpc.socialG This user is from outside of this forum
    ghostwriter@phpc.socialG This user is from outside of this forum
    ghostwriter@phpc.social
    wrote last edited by
    #1

    #GitHub was compromised again… via a poisoned #VSCode extension.

    X Cancelled | Verifying your request

    favicon

    (xcancel.com)

    X Cancelled | Verifying your request

    favicon

    (xcancel.com)

    wdormann@infosec.exchangeW 1 Reply Last reply
    0
    • ghostwriter@phpc.socialG ghostwriter@phpc.social

      #GitHub was compromised again… via a poisoned #VSCode extension.

      X Cancelled | Verifying your request

      favicon

      (xcancel.com)

      X Cancelled | Verifying your request

      favicon

      (xcancel.com)

      wdormann@infosec.exchangeW This user is from outside of this forum
      wdormann@infosec.exchangeW This user is from outside of this forum
      wdormann@infosec.exchange
      wrote last edited by
      #2

      @ghostwriter
      A "poisoned" VSCode extension...

      Does that convey a legitimate extension that was compromised (in what way?)?

      Or a VSCode extension that is inherently malicious?

      I feel like there's an important difference.

      wdormann@infosec.exchangeW 1 Reply Last reply
      0
      • wdormann@infosec.exchangeW wdormann@infosec.exchange

        @ghostwriter
        A "poisoned" VSCode extension...

        Does that convey a legitimate extension that was compromised (in what way?)?

        Or a VSCode extension that is inherently malicious?

        I feel like there's an important difference.

        wdormann@infosec.exchangeW This user is from outside of this forum
        wdormann@infosec.exchangeW This user is from outside of this forum
        wdormann@infosec.exchange
        wrote last edited by
        #3

        @ghostwriter
        Ah, apparently it was compromised

        1 Reply Last reply
        1
        0
        • R relay@relay.infosec.exchange shared this topic
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

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