this post was submitted on 31 Mar 2026
36 points (100.0% liked)

Programming

26304 readers
608 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
all 12 comments
sorted by: hot top controversial new old
[–] dosse91@lemmy.trippy.pizza 9 points 20 hours ago (1 children)

Because in web development it is perfectly normal to use 2 frameworks and 1200 random libraries to do the simplest of things. One compromised library will compromise all applications that rely on it directly or indirectly, no matter how small.

I absolutely hate this aspect of web development and frankly I'm scared every time I type npm install

[–] who@feddit.org 4 points 20 hours ago* (last edited 20 hours ago)

And it's not just web development.

This mindset has been spreading for... probably decades. Nowadays, it is even pushed by certain popular programming languages, by including a toolchain that makes it as easy as possible to pull in third-party dependencies while offering a standard library so minimal that a developer is strongly encouraged to rely on said dependencies.

This inevitably leads to a world where software supply chain attacks have massive reach and high chances of success. And threat actors take advantage of it, of course.

[–] vane@lemmy.world 2 points 16 hours ago

Because of centralization, open source exploitation by multi billion dollar corporations, high costs of living and overall size and impact of the industry. When industry was small full of developers it was more cozy, now developers are minority in IT industry so the practices from different areas take place. Instead of collaboration and helping each other we see people mostly competing and fighting. Managers that were brought to software from different areas are encouraging people to do so. Everyone is complaining but nobody is willing to help to change something because corporate make profit, C-Levels earn hundreds of millions and shareholders are happy.

[–] trackball_fetish@lemmy.wtf 4 points 21 hours ago

Because, its easier to catch many fish with a large net than many fish with a small one

[–] moonpiedumplings@programming.dev 26 points 1 day ago* (last edited 1 day ago)

Debian Linux, and many other Linux distros, have extensive measures to protect their supply chain. Packages are signed and verified, by multiple developers, before being built reproducibly (I can build and verify and identical binary/package). The build system has layers, such that if only a single layer is compromised, nothing happens and nobody flinches.

Programming langauge specific package repos, have no such protections. A single developer has their key/token/account, and then they can push packages, which are often built on their own devices. There are no reproducible build to ensure the binaries are from the same source code, and no multi-party signing to ensure that multiple devs would need to be compromised in order to compromise the package.

So what happened, probably, is some developer got phished or hacked, and gave up their API key. And the package they made was popular, and frequently ran unsandboxed on devs personal devices, so when other developers downloaded the latest version of that package, they got hacked too. The attackers then used their devices to push more malicious packages to the repo, and the cycle repeats.

And that's why supply chain attacks are now a daily occurrence.

[–] tal@lemmy.today 13 points 1 day ago* (last edited 1 day ago)

https://xkcd.com/2347/

The guy in Nebraska probably has fewer resources to protect against you than the sum total of all of the downstream companies that you're trying to attack.

[–] 9point6@lemmy.world 9 points 1 day ago

Because they're pretty effective currently

[–] Kissaki@programming.dev 6 points 1 day ago
  • Huge growth in tooling and systems making use of "community" dependencies
  • Fewer safeguards and security guarantees and concerns on these platforms
  • Easy entry into these platforms and systems
  • Huge potential scale-effect through global software development tooling
  • Huge additional potential scale effect through developer and development systems - crossing into other such platforms through local credentials, immediate access to internal tooling, platforms, and systems, and potential to attack other downstream systems and platforms
  • Public knowledge about the attack vectors, attack successes and reporting, and continued opportunity, occurrence, and personal successes, investment, and knowledge

They are easy and effective

[–] BB_C@programming.dev 3 points 1 day ago

how many real-world attacks happened since the XZ fiasco outside of the webshit ecosystem?

Is it the attacks themselves that have become a daily occurrence, or the detection thereof?