@lucideproxy/svg@0.0.31
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not concrete npm malware: it has no lifecycle hooks or Node execution path. It should nevertheless warn because it ships an obfuscated, browser-executed web-proxy stack that can relay authenticated user traffic.
Decision evidence
public snapshot- Runtime registers a service worker that routes requests through a proxy.
- Boot code creates a Wisp proxy transport and controller.
- Fingerprint module sends monitoring traffic to m1.openfpcdn.io.
- Settings bundle is deliberately obfuscated.
- package.json has no lifecycle scripts, bin, or package entrypoints.
- Manifest describes a static proxy-site bundle.
- No Node child-process, filesystem, env-harvesting, or install-time execution found.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-8bb51b6b.jsView on unpkg · L13Package source references dynamic require/import behavior.
hn2rh/gu3e68.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.31.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.31 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.