@lucideproxy/svg@0.0.60
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not a normal SVG package: its executable SVG launches an obfuscated service-worker proxy. The absence of install hooks and confirmed theft supports a warning rather than a malware block.
Decision evidence
public snapshot- The declared SVG is an executable HTML document inside foreignObject, not an icon asset.
- Opening the SVG loads two opaque bundles and dynamically imports the application.
- The browser application registers a service worker.
- The service worker intercepts routed fetches and forwards them to its proxy router.
- The package ships an opaque proxy runtime and WebAssembly module despite having no normal SVG exports.
- The manifest contains no npm lifecycle scripts or Node entry point.
- The proxy activates only when a user opens the bundled SVG or site; installation alone does not run it.
- No source evidence showed local credential harvesting, shell execution, or npm-project mutation.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-8ac1fed7.jsView on unpkg · L13Package source references dynamic require/import behavior.
lob5r/zzfvmn.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.60.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.60 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.