HackerPapers

arXiv:2411.07479cs.CR

Developers Are Victims Too : A Comprehensive Analysis of The VS Code Extension Ecosystem

Shehan Edirimannage, Charitha Elvitigala, Asitha Kottahachchi Kankanamge Don, Wathsara Daluwatta, Primal Wijesekara, Ibrahim Khalil

Early discovery. Linked by one identifiable commenter. This paper is outside the main ranking; a mention is not an endorsement.

Abstract

With the wave of high-profile supply chain attacks targeting development and client organizations, supply chain security has recently become a focal point. As a result, there is an elevated discussion on securing the development environment and increasing the transparency of the third-party code that runs in software products to minimize any negative impact from third-party code in a software product. However, the literature on secure software development lacks insight into how the third-party development tools used by every developer affect the security posture of the developer, the development organization, and, eventually, the end product. To that end, we have analyzed 52,880 third-party VS Code extensions to understand their threat to the developer, the code, and the development organizations. We found that ~5.6\% of the analyzed extensions have suspicious behavior, jeopardizing the integrity of the development environment and potentially leaking sensitive information on the developer's product. We also found that the VS Code hosting the third-party extensions lacks practical security controls and lets untrusted third-party code run unchecked and with questionable capabilities. We offer recommendations on possible avenues for fixing some of the issues uncovered during the analysis.

arXiv comments
Journal reference
DOI
Subjects
cs.CRCryptography and Security cs.SESoftware Engineering

On Hacker News

Linked by 1 identifiable commenter in 2 comments across 2 threads, from Nov 2024 to Jan 2025.

Comments linking this paper, per year.

Discussed in comments2 threads

  1. Why I Chose Common Lisp 1 comment
    • > VS Code managed to by-pass the qualitiy and amount of extensions/plugins in a fraction of time Emacs took decades. I get the impression that the VSCode has a rather fractured, limited, malware-infested[1][2], JavaScript-churn inundated plugin ecosystem. You have lots of…

      uludagView on HNParent context

    • I have no doubt that VSCode has a much less risk of executing code by opening something. Ironically however, it seems that VSCode's extension is the most effective channel to distribute malware in the history of code editors. [1] [2] Not that MELPA couldn't be used to distribute…

      uludagView on HNParent context

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.