False Positive Malware Flag on @znan/wabot (GHSA-2jxx-8fv2-h8mj)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript
- Domain
- security
Research direction
Start by reviewing the unobfuscated source in the znanx/wabot repository and comparing it with the published @znan/wabot package associated with GHSA-2jxx-8fv2-h8mj. Confirm whether the malware flag is a false positive caused by JSConfuser obfuscation; completion would require the GitHub Security Team to review and remove or correct the advisory flag.
Written by the indexing model from the issue text.
Description
False Positive Malware Flag on @znan/wabot (GHSA-2jxx-8fv2-h8mj)
Hello GitHub Security Team,
I am the author and maintainer of the npm package @znan/wabot and the repository znanx/wabot. My package was recently flagged as malware under GHSA-2jxx-8fv2-h8mj.
I would like to clarify that this is a false positive caused by code obfuscation, not malicious functionality. I use a tool called js-confuser to obfuscate the JavaScript output before publishing.
To be precise about my repo/publish setup: the original source code lives in a private repository. When I push changes there and create a release tag, the pipeline automatically builds the project, obfuscates the JS output with js-confuser, mirrors that obfuscated build to this public repository (znanx/wabot), and publishes the same obfuscated build to npm as @znan/wabot. So this public repo and the npm package contain the same obfuscated code, not the original readable source.
I'm glad to grant a reviewer temporary read access to the private repository so the unobfuscated source can be checked directly against the published build, or to walk through any specific function that triggered the detection.
My npm account has also been locked due to this automated flag. Could you please review the source and remove the malware advisory flag from my package? I am fully prepared to either republish the package unobfuscated, or declare it as dual-use content (contentPolicy + DISCLOSURE) if that helps avoid this in the future.
Thank you for your time and help.
(Edit: corrected an earlier inaccurate statement about the public repo containing unobfuscated source — it does not; the original source is private.)
- 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 78/100
punkpeye/mcp-remote#369 ·
-
Mend: dependency security vulnerability untriaged
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
cisagov/vulnrichment#337 ·
-
bug DUP Reservations
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bcgov/reserve-rec-public#896 ·