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

まず、znanx/wabot リポジトリの難読化されていないソースを確認し、GHSA-2jxx-8fv2-h8mj に関連付けられた公開済みの @znan/wabot パッケージと比較します。マルウェアフラグが JSConfuser による難読化が原因の false positive であるかを確認してください。完了には、GitHub Security Team が 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.)