Re:What NPM should do to stop a new colors attack
by Isthatablackgsd on Monday January 10, 2022 @01:00PM
(#29878755)
I agree with awinter-py, it will be tricky to use "without authorization" for this. The developer only published the code, that is up to other companies to verify the code and roll with it. If Company A installed the dependency, that could mean Company A "authorized" the code because they pulled the dependency to their system. So not sure how CFAA could protect this if the Company A proceed to download the code which in turn that the code are authorized. It is their responsibility to audit and verify the code before incorporating into their software.
[ Parent
| on HN ]
Re:What NPM should do to stop a new colors attack
by DangitBobby on Monday January 10, 2022 @09:26PM
(#29886522)
Is it considered "authorized" if I knowingly visit a website but did not realize it would execute malicious JavaScript on my machine? Anyone who unknowingly installed this malicious package in their project is having that same problem.