Live data from Hacker News

Major bank accidentally published a private package to the public NPM Registry

twitter.com

61–70 of 236 posts

Re: Major bank accidentally published a private package to the public NPM Registry

#61
post #30

It took them no less than 3 years to actually notice... Holy moly! I wonder what package that is... Just out of curiosity...

You'd think it's like, some proprietary trading algorithm, but in reality it's probably their own implementation of left-pad.

It was a react package.

Source: https://twitter.com/seldo/status/1105157348560007168?s=09

Re: Major bank accidentally published a private package to the public NPM Registry

#62
post #33

Earlier quoted context omitted.

How is this DMCA abuse? A copyright owner is requesting that a site that has safe harbor protection remove an unauthorized copyrighted work. The employee that originally created the unauthorized package may no longer work for the bank, unable to be identified, or doesn't have the credentials anymore.

Does the fact that the bank distributed the material in the first place change the situation?

No. The Bank's intent is what matters, not the intent or actions of a single employee.

Re: Major bank accidentally published a private package to the public NPM Registry

#63
post #36

Is this client side code? Unless this is internal wouldn't it be available when visiting there website?

Probably doesn't matter to their legal team. All code is company IP so they don't want it posted anywhere unnecessarily.

Tweet thread says it's a react packaged which means it's probably usually transpiled and minified, so not technically available in its original form in its distributed application.

Re: Major bank accidentally published a private package to the public NPM Registry

#64

Earlier quoted context omitted.

I’m not sure how universally true that is. When governments fail to redact documents, it’s on them. If you “accidentally” talk to a reporter about your solicitor-privileged comms, it’s not privileged anymore.

This isn't an open question. If you don't have a license from the copyright holder, you can't legally use it, except for fair use exemptions: perhaps you could write a blog post criticizing it.

Was there a licence attached to the files? What if there wasn’t

Re: Major bank accidentally published a private package to the public NPM Registry

#65
Slightly off topic, but my experience with lawyers and technology has been mostly discouraging. For example, one lawyer wanted to sue a client of ours for using an open-source JS dropdown menu that we were also using--he said they stole our code. He was also concerned that we were letting people 'View Source' our web pages and stealing our IP.

Re: Major bank accidentally published a private package to the public NPM Registry

#66

Earlier quoted context omitted.

This isn't an open question. If you don't have a license from the copyright holder, you can't legally use it, except for fair use exemptions: perhaps you could write a blog post criticizing it.

Was there a licence attached to the files? What if there wasn’t

> If you don't have a license from the copyright holder, you can't legally use it, except for fair use exemptions: perhaps you could write a blog post criticizing it.

Re: Major bank accidentally published a private package to the public NPM Registry

#69
post #62
post #33

Earlier quoted context omitted.

Does the fact that the bank distributed the material in the first place change the situation?

No. The Bank's intent is what matters, not the intent or actions of a single employee.

That is absolutely not true, and it flies in the face of the notion of "due diligence".

This bank uploaded their own code to the repo, and when they found it they didn't bother to do any investigating before they started sending legal demands.

It was 100% their responsibility to ensure that they were not responsible for their own leak before they started making legal threats.

They decided to skip due diligence, and they should pay the price for wasting others' time and energy, regardless of their "intentions".

Re: Major bank accidentally published a private package to the public NPM Registry

#70
post #58

Why not just take it down? What do you need a lawyer for ? Isnt there an option for deleting your own packages ?

You would think so, but perhaps they didn't have the credentials.

They never contacted a human at npm, they just went straight over their heads.
Post reply on HN