@lucideproxy/svg@0.0.63
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source establishes a cookie-bearing browser proxy behind obfuscated code, which is unsafe and inconsistent with a normal SVG package. There is no install lifecycle or Node-side execution, so static inspection does not establish install-time malware.
Decision evidence
public snapshot- The published SVG and HTML automatically load an obfuscated browser application and analytics.
- The browser application registers a service worker and configures a proxy controller.
- The proxy runtime reads and forwards proxied-site cookies with WebSocket requests.
- package.json has no lifecycle hooks, dependencies, executable entry points, or self-dependency.
- No Node execution, project-file mutation, shell command, or install-time behavior was found.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-50790430.jsView on unpkg · L13Package source references dynamic require/import behavior.
o68rt/rf2xmd.jsView on unpkg · L17Source contains an obfuscated payload loader that reconstructs and executes hidden code.
assets/AccountPage-DjgbyHPx-50790430.jsView on unpkg · L1Source file is highly similar to a previously finalized malicious package; route for source-aware review.
assets/fingerprint-Y5nV5FVa-50790430.jsView on unpkgFindings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.63.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.63 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.