@lucideproxy/svg@0.0.41
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains an obfuscated, dynamically evaluated browser proxy rather than an SVG library, which is a real dangerous capability. Its activation is user-driven site loading rather than an unconsented npm lifecycle action, and no concrete theft or destructive chain was confirmed.
Decision evidence
public snapshot- Obfuscated main bundle reconstructs code with `new Function`.
- The served application registers a service worker, claims clients, and routes matching fetches through its proxy runtime.
- Package contents are a browser proxy application, not an SVG library.
- No npm lifecycle scripts or Node entrypoints are declared.
- No credential harvesting, shell execution, or concrete third-party exfiltration endpoint was confirmed.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-9e93a8da.jsView on unpkg · L13Package source references dynamic require/import behavior.
assets/motion-ClYBgd9J-9e93a8da.jsView on unpkg · L8Findings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.41.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.41 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.