@lucideproxy/svg@0.0.39
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete npm install-time compromise was found, so blocking as malicious is not justified. The concealed browser proxy and dynamic runtime are materially unsafe and unrelated to the claimed package purpose.
Decision evidence
public snapshot- Not an SVG library: it ships a browser proxy application and service-worker fetch interceptor.
- Main browser bundle is deliberately obfuscated and constructs executable code with `new Function`.
- The application includes an obfuscated AI client that sends fingerprint headers and credentialed fetches.
- A bundled WebAssembly module expands the opaque browser-runtime payload.
- package.json has no lifecycle scripts, bin, main, or exports entrypoint.
- npm installation alone does not execute the browser assets; activation requires serving/opening the site.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-f0c31c9b.jsView on unpkg · L13Package source references dynamic require/import behavior.
q8mgt/mvvk9u.jsView on unpkg · L17Source contains an obfuscated payload loader that reconstructs and executes hidden code.
assets/AiPage-VB4B81NT-f0c31c9b.jsView on unpkg · L1Source file is highly similar to a previously finalized malicious package; route for source-aware review.
assets/fingerprint-Y5nV5FVa-f0c31c9b.jsView on unpkgFindings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.39.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.39 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.