@neoxr/zapo
TypeScript connector for building WhatsApp Bot (ZapoJS)
This report shows the evidence for @neoxr/zapo@1.2.11. 1 of 8 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe entrypoint actively conceals and executes embedded code, and exits when debugging is detected. This is concrete malicious behavior rather than an inert WebAssembly carrier.
Decision evidence
public snapshot- The package entrypoint is lib/index.js.
- The entrypoint exits when it detects an inspector or debugging activity.
- It loads and instantiates an embedded WebAssembly module, then uses it to process package metadata and encoded data.
- It decompresses the WebAssembly output and executes the result as JavaScript with access to Node module objects.
Source & flagged code
6 flagged · loading sourcePackage declares a runtime dependency whose name matches a Node built-in module.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @neoxr/zapo@1.2.11.
The versions list below shows the verdict for each recorded version.
- Avoid installing @neoxr/zapo@1.2.11. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.