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

Erroneous malware reports on appdynamics-* packages #5026

Closed
laurie71 opened this issue Nov 20, 2024 · 3 comments
Closed

Erroneous malware reports on appdynamics-* packages #5026

laurie71 opened this issue Nov 20, 2024 · 3 comments

Comments

@laurie71
Copy link

There are three malware reports against packages published by AppDynamics:

I work for AppDynamics (a Cisco, Inc business unit) and am the lead engineer for the product these packages are a part of. These packages are not malware, do not contain malware, and do not have any vulnerabilities listed by npm audit. I believe the malware reports against them are, at best, erroneous and, at worst, malicious.

Unfortunately the advisories linked above contain no specifics that we can address. What is the process for refuting these advisories and getting them removed?

@darakian
Copy link
Contributor

Hey @laurie71, these are legitimate advisories which were generated as part of a malware take down done by the npm team. The advisories are specifically about the packages on npmjs.com
ex. https://www.npmjs.com/package/appdynamics-libagent-napi

And I would guess that your build system is using a private package registry for packages of the same name. If you do some searching you'll find similar issues others have opened in this repo
ex.
#3487
#4697
#2492

tl;dr is that npm audit is confusing where packages come from. I opened an issue with npm some time back to try and get this addressed in default behavior for npm audit, but alas no movement there
See: npm/rfcs#739

So, you can reach out to npm support about these advisories, but the packages on npmjs.com were almost certainly malware and having advisories about them is beneficial for anyone who may have downloaded those packages. Sorry, I can't give you a more satisfying answer, but I hope that helps at least 😃

@laurie71
Copy link
Author

Ah, that explains it; glad they were taken down. I'll follow up with npm support.

@darakian
Copy link
Contributor

Cool. Well if you're good then I'll close this issue out. Feel free to re-open/reply/whatev too if I can help more 👍

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