At some point, npm supply chain attacks are going to stop being news and start being "Tuesday."
... JS on the backend was a mistake.
this post was submitted on 17 Sep 2023
76 points (97.5% liked)
Programming
17000 readers
232 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 1 year ago
MODERATORS
JS was a mistake.
It wouldn't have been if it kept to the original purpose of some simple tasks and such, but we can't have nice things.
JS on the backend was a mistake.
Typo squatting is not unique to JS.
True, but it's uniquely bad in the JS world. Developers tend to rely on libraries in almost cartoonish excess.
- The language is shit in general, leading to an endless parade of frameworks and packages designed to paper over the sore spots.
- The lack of a well-rounded One True Standard Library™ means lots of trivial functionality needs to come from somewhere.
- Micro-dependencies are commonplace, leading to bloated dependency trees. I'd guess this is caused by a combination of both culture and the fact that you often want your JS artifacts to be as lean as possible.
Clickbait title.
The packages were collectively downloaded 963 times before they were removed. The rogue packages include names like "noblox.js-vps," "noblox.js-ssh," and "noblox.js-secure," and they were distributed across specific version ranges
Is there any indication that anyone actually installed these, other than some bots that auto download all packages and such?
You would have to really go out of your way to get infected by stuff like this.
That being said, there are things npm could do to try to auto-detect "risky" packages (new, similar name to existing projects, few downloads, etc.) and require an additional layer of confirmation, or something like that.
Also, as far as I can tell, they’re talking about devs that are building on the Roblox platform, not devs that are building the platform.
In other words, random devs of varying skill levels getting name-squatted.
It’s not good, but including Roblox in the title is definitely misleading/clickbait.
It is a library to work with Roblox, saying Roblox isn't misleading. I can agree that "Roblox devs" is misleading though.
It’s misleading because it’s irrelevant and makes it sound like a platform breach.
Try replacing Roblox with “Foozsplatz” and the implication of severity is completely different, even though the nature of what is being reported is unchanged.
I'm confused, in this hypothetical is Foozsplatz a non sense word or is it meant to be a game like Roblox? If you mean the first, then yeah, obviously replacing a proper noun with gibberish changes the implication. If you mean the second then no, it would have the same implication.
It literally doesn’t matter. You can remove the word and the nature of the problem being discussed is still the same. What platform is being targeted has nothing to do with the example problem. Roblox is only mentioned to sensationalize it and get clicks.
Roblox is mentioned because it literally was a library for Roblox lmao. That's not sensationalizing.
The thread you are in and my response made it clear that the headline is clickbait by including that irrelevant detail.
If they didn’t include that word in the post title, it would have no traction at all.
"Roblox library is target of typo squatting" is a perfectly accurate headline that uses the word Roblox and is not clickbait.
That’s why we need script blockers by default.