False Positive Malware Flag on @znan/wabot (GHSA-2jxx-8fv2-h8mj)

Inizia esaminando il codice sorgente non offuscato del repository znanx/wabot e confrontandolo con il pacchetto pubblicato @znan/wabot associato a GHSA-2jxx-8fv2-h8mj. Conferma se la segnalazione di malware è un false positive causato dall’offuscamento di JSConfuser; per completare il lavoro sarebbe necessario che il GitHub Security Team esaminasse e rimuovesse o correggesse la segnalazione dell’advisory.

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.)