Jump in the discussion.

No email address required.

Oh wow a NPM vulnerability. Truly a day ending :y:.

Jump in the discussion.

No email address required.

>In 2012, the “hoarders” package, described by its creators as “node.js's most complete ‘utility grab-bag,'” created dependencies for all 20,000 modules published in the NPM registry at the time.

>20,000 dependencies

So pretty much a normal JS project? This stuff is barely parody.

Jump in the discussion.

No email address required.

due to an apparent prank gone wrong

:marseyconfused:

Jump in the discussion.

No email address required.

JavaScript

Jump in the discussion.

No email address required.

boomers literally shitpost a language in 1995

>this is fine

Jump in the discussion.

No email address required.

NPMcels deserve all this and worse.

Jump in the discussion.

No email address required.

This website has aids

https://i.rdrama.net/images/1704403778617559.webp

Jump in the discussion.

No email address required.

Same

Jump in the discussion.

No email address required.

ublock chads stay winning

https://i.rdrama.net/images/17044067973343477.webp

Jump in the discussion.

No email address required.

U can't block :marseyerasure: my aids riddled peepee in ur butt

Jump in the discussion.

No email address required.

o yes i can

My people have evolved to have butthair stronger than steel and the fine musculature to be able to control it; your hog will be like a large bird trying to fly through a chain linked fence.

Jump in the discussion.

No email address required.

Npm is a joke package manager

Jump in the discussion.

No email address required.

Javascript is a dark comedy

Jump in the discussion.

No email address required.

TBF, all package managers are shitty :marseycodecelgenocide:

Jump in the discussion.

No email address required.

On Dec. 29, a package titled “everything” was published to the registry, which is designed to install all other public packages in the registry. This created a registry-wide web of dependencies that effectively disabled the ability to unpublish packages on the site, as packages that other packages are dependent on cannot be unpublished.

The incident triggered responses from developers left unable to unpublish their deprecated or experimental packages, as well as criticism from some who viewed the stunt as an abuse of the open-source NPM system.

The developers behind “everything” said they did not anticipate these consequences and reached out to NPM and GitHub to resolve the issue. Ironically, the team was left unable to unpublish “everything” themselves due to a circle of dependencies that essentially made the package dependent on itself.

“We just thought it would be funny,” wrote Evan Boehs, an “everything” contributor, in response to another GitHub user's question about the project's purpose. “We did not know all this would happen.”

The “everything” package was accompanied by a “README” file stating “Please don't actually install this…” It also included a meme image of Gary Oldman from the film “Léon,” depicting a scene in which Oldman's character dramatically shouts the word “everyone.”

https://media.giphy.com/media/sUNqplVFtsctW/giphy.webp

The “about” section of the “everything” repository also includes a link to the website “everything.npm.lol,” which displays an animation depicting numerous packages being installed followed by a meme from the video game “The Elder Scrolls V: Skyrim.”

Despite the warning to not install the package, the NPM registry site indicates “everything” was downloaded 224 times as of Jan. 3.

Jossef Harush, head of the supply chain security engineering group at Checkmarx, said in a blog post that installing “everything” would likely result in a denial of service (DoS). Harush also refers to the project as a “troll campaign.”

“I want to reiterate that we aren't trolls, we are at worst QA testers for NPM, and at best comedians and creative coders,” Boehs wrote separately in a comment on GitHub.

The sweeping effect of “everything” across the entire NPM registry exposes flaws in the NPM open-source system, argues contributor PatrickJS on GitHub, who goes by the username gdi2290 on the NPM site.

“to be clear this is an edge-case in NPM's unpublish policy which doesn't account for ‘,'” PatrickJS wrote on GitHub, referring to the star symbol that indicates a package's dependency on any and all versions of another package. PatrickJS suggested that GitHub should allow developers to unpublish a package if its dependents rely on “star versions,” or disable this use of “” altogether.

“One other thing to note while discussing this fiasco, we considered that this could have been exploited for much more malicious reasons,” said fellow contributor Boehs. “Say, if somebody accidentally uploads sensitive information, a bad actor could make packages to keep it up. It's good this was caught in this way instead of after being exploited in the wild.”

Some other developers were not convinced, expressing frustration and disapproval on the “everything” repository's issues board.

One user, Matt Lupeepee, lambasted the group for “reckless negligence” and for blaming NPM for the fallout of their project.

“You have deluded yourselves into believing that the problem isn't that you abused the registry, but that npm's unpublish rules don't hold up to someone abusing the registry in this way,” Lupeepee wrote, adding that the unpublish rules are necessary “protect the integrity of the registry.”

:soysnooseethetalking:

Nicolas Ventura, a data center engineer at Lawrence Berkeley National Lab, reported that one of his deprecated packages was impacted by the dependency issue, and said that while the project was “interesting and humorous,” it ultimately caused unnecessary problems.

“This project certainly feels like spam and the thousands of sub-packages should not have been published to the official NPM repository and are just causing clutter,” Ventura wrote. “I'm fascinated that NPM didn't flag or block any packages from being published, since many other websites, like social media has posting limits.”

The “everything” package, which has more than 3,000 sub-packages, remains published on the NPM registry as of this writing, although PatrickJS reported that GitHub was actively working to fix the issue since Tuesday night.

Lupeepee and Harush note previous instances of developers publishing NPM packages that created a stir due to the creation of registry-wide dependencies.

In 2012, the “hoarders” package, described by its creators as “node.js's most complete ‘utility grab-bag,'” created dependencies for all 20,000 modules published in the NPM registry at the time. The project received backlash and was later revised to work without creating direct dependencies to the utilities it installs.

More recently, in January 2023, a package called “no-one-left-behind” was made dependent on all other packages in the NPM registry. The package was removed by NPM, which labeled it as containing “malicious code,” although more than 33,000 subpackages of “no-one-left-behind” continued to exist, causing some difficulty.

Jump in the discussion.

No email address required.

It also included a meme image of Gary Oldman from the film “Léon,” depicting a scene in which Oldman's character dramatically shouts the word “everyone.”

that was such a good scene too

Jump in the discussion.

No email address required.

I want the pills he takes

Jump in the discussion.

No email address required.

:marseynotes:

if i need to get frozen a birthday present... get her pills...

Jump in the discussion.

No email address required.

bruh i permalurk and even i knew that :marseyexcited:

Jump in the discussion.

No email address required.

You have deluded yourselves into believing that the problem isn't that you abused the registry

It's your fault we made an impressively broken system :marseymad:

Jump in the discussion.

No email address required.

What?

Jump in the discussion.

No email address required.

NOOOOOOOO! I. MUST. POOOOOOOOBLISH!!!!!

Jump in the discussion.

No email address required.

>"We found the project to be in violation of GitHub's Acceptable Use Policies, which prohibit behavior that significantly or continually disrupts the experience of other users. It was also found to violate the npm Code of Conduct,"

I hate when my EULA violations disrupt my systems.

Jump in the discussion.

No email address required.

"we are at worst QA testers for NPM"

Oh great, rogue QA testers, definitely not my worst nightmare or anything

Jump in the discussion.

No email address required.

NPM users get what they deserve

Jump in the discussion.

No email address required.

Lol I'm sure they implemented this stupid policy because of the left-pad incident. Given the stupidity of codecels in the first place and their need to import a dependency for the most trivial of tasks, the “everything” incident is probably the least bad incident which could happen to NPM.

Any software team not pulling dependencies from a private registry for their own applications/libraries should be fired.

:#marseycodecelgenocide:

Jump in the discussion.

No email address required.

Who ever user "snappy" is. He needs to be permanently banned. NO warning , banishment. Scroll down to his post on this page. It's pure bullshit. And he's posting pure gibberish.

Snapshots:

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.