Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coa #9

Closed
vielmetti opened this issue Nov 4, 2021 · 5 comments
Closed

coa #9

vielmetti opened this issue Nov 4, 2021 · 5 comments

Comments

@vielmetti
Copy link

Noted at https://twitter.com/npmjs/status/1456310581846163457

From the advisory:

The npm package coa had versions published with malicious code. Users of affected versions (2.0.3 and above) should downgrade to 2.0.2 as soon as possible and check their systems for suspicious activity. See this issue for details as they unfold.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This issue veged/coa#99 has the play-by-play

@vielmetti
Copy link
Author

@vielmetti
Copy link
Author

The analysis from Bleeping Computer suggests that the attack is very similar to what happened to ua-parser-js, #4 .

@adityasaky
Copy link
Owner

I'll submit to the CNCF list. Interesting how much this broke, and how quickly it was detected...

@adityasaky
Copy link
Owner

Thanks, @vielmetti!

@vielmetti vielmetti mentioned this issue Nov 4, 2021
@adityasaky
Copy link
Owner

Added to cncf/tag-security#812

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants