@zakir300408/wechat-companion@0.1.0
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-20133 confirms this npm version as malicious.
OpenSSF/OSV advisory MAL-2026-20133 confirms this npm version as malicious.
LPM's AI review of this version remains unresolved. The OpenSSF/OSV advisory supplies the block.
The readable JavaScript and documentation describe a read-only WeChat MCP companion with user-controlled pairing. The native app launches during setup and handles the documented tunnel workflow, but the supplied analysis could not inspect it, leaving key credential and transmission behavior unverified.
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
package.json1 highcli.cjs1 highserver.mjs1 high · 1 mediumREADME.md1 highCompanion.exe1 mediumInstall.ps11 mediumpackage.json1 findingcli.cjs1 findingserver.mjs2 findingsREADME.md1 findingCompanion.exe1 findingThe visible MCP server exposes conversation and message reading tools, with attachment reads limited to handles issued for retrieved messages.
server.mjsView on unpkg · L33Package source references dynamic require/import behavior.
server.mjsView on unpkg · L13The package is a Windows WeChat companion whose CLI runs the installer only when the user invokes setup.
package.jsonView on unpkg · L5The package is a Windows WeChat companion whose CLI runs the installer only when the user invokes setup.
cli.cjsView on unpkg · L13The README says tunnel keys are stored with Windows DPAPI and passed to the tunnel process through its environment.
README.mdView on unpkg · L22This report applies to @zakir300408/wechat-companion@0.1.0.
See all versions of @zakir300408/wechat-companion for other recorded verdicts.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.
Install.ps11 finding