@neoxr/zapo@1.0.1
TypeScript connector for building WhatsApp Bot (ZapoJS)
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe dependency hints do not prove malware, but source inspection establishes automatically invoked, heavily obfuscated executable code with module-loading access. A warning is warranted for unresolved import-time behavior; the available evidence does not support blocking as malicious.
Decision evidence
public snapshot- The manifest declares path as a runtime dependency; this metadata alone does not establish malicious behavior.
- lib/index.js automatically imports lib/utils/security.js.
- lib/utils/security.js constructs executable code from extensively obfuscated string lookups using Function.
- The constructed function is immediately invoked with access to require and mutable exports, leaving its import-time behavior unresolved.
- The manifest has no installation lifecycle scripts or runtime self-dependency.
- No concrete exfiltration destination, destructive operation, or agent control-surface mutation was established.
Source & flagged code
5 flagged · loading sourcePackage declares a runtime dependency whose name matches a Node built-in module.
package.jsonView on unpkgThe manifest declares path as a runtime dependency; this metadata alone does not establish malicious behavior.
package.jsonView on unpkg · L47lib/index.js automatically imports lib/utils/security.js.
lib/index.jsView on unpkg · L47Findings
Affected versions and remediation
This report applies to @neoxr/zapo@1.0.1.
See all versions of @neoxr/zapo for other recorded verdicts.
- Review the evidence and your use of @neoxr/zapo@1.0.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.