URGENT: False Malware Classification of google-img-scrap - Request for Immediate Review
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, node.js
- Domain
- security
Research direction
Start by reviewing advisory GHSA-mwh7-p59x-2f4g and the google-img-scrap repository linked in the issue. Compare the advisory's all-versions malware classification with the project's source and the requested specific versions, files, commits, or behavior. Done means the classification is supported with technical evidence or corrected or removed if it cannot be substantiated.
Written by the indexing model from the issue text.
Description
I am the original author and maintainer of google-img-scrap and I am disputing this advisory.
The advisory GHSA-mwh7-p59x-2f4g incorrectly classifies the entire google-img-scrap package as malware and states that all versions are malicious.
I have reviewed the project and its source code, and I do not agree with this classification. The advisory provides no technical evidence, malicious file, malicious commit, affected code path, or specific malicious behavior supporting the claim that all versions of the package are malware.
In particular, the statement that all versions (>= 0) are malicious is extremely broad and does not identify any specific vulnerability or malicious functionality.
I am the legitimate maintainer of the package and would like GitHub to review this advisory and its underlying evidence.
Please provide the technical evidence supporting this classification, including the specific version(s), file(s), commit(s), or behavior that were determined to be malicious.
If the advisory cannot be substantiated, I request that it be removed from the GitHub Advisory Database and that any resulting malware/security classification associated with the package be corrected.
This advisory is also having significant consequences for the project and its users, including the removal or blocking of all my npm package, so I would appreciate an urgent review.
Repository:
https://github.com/yoannchb-pro/google-img-scrap
- Dominant language
- No language data
- Stars
- 2.5k
- Forks
- 772
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 48
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/advisory-database
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#9255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#9164 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8994 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/advisory-database#8898 · 4 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/advisory-database#8841 ·
All issues in github/advisory-database
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docToolchain/docToolchain#1705 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3566 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·