@lucideproxy/svg
Lucide SVG build: static proxy site bundle served from index.svg
This report shows the evidence for @lucideproxy/svg@0.0.65. 8 of 40 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe automatic SVG import, deliberate obfuscation, and dynamic code execution are incompatible with a passive SVG package. Lack of install hooks reduces install-time risk but does not remove the rendering-time payload risk.
Decision evidence
public snapshot- The SVG automatically imports a large obfuscated JavaScript bundle when rendered.
- The imported bundle dynamically constructs and invokes code with new Function.
- The package disguises an interactive proxy-style web application and worker as an SVG package.
- The manifest has no npm lifecycle hooks or Node entry points.
- The observed execution requires rendering the packaged SVG; it does not run during installation.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-210c06f6.jsView on unpkg · L13Package source references dynamic require/import behavior.
83hpv/v92iw5.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.65.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lucideproxy/svg@0.0.65. 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.