@lucideproxy/svg@0.0.59
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe artifact is not an SVG library and exposes an obfuscated proxy/cookie-control surface at browser runtime. Its lack of npm lifecycle or import entrypoints prevents a publish block under the concrete-attack threshold.
Decision evidence
public snapshot- Rendering index.svg auto-loads the bundled proxy and app scripts.
- The service-worker bridge transfers cookies into a proxy client.
- The main browser bundle is deliberately obfuscated and uses new Function.
- AiPage sends a generated fingerprint header in fetch requests.
- package.json has no lifecycle scripts, bin, main, or module entrypoint.
- No confirmed credential theft, filesystem access, shell execution, or malicious endpoint was recoverable from source.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-59094c2b.jsView on unpkg · L13Package source references dynamic require/import behavior.
byvmk/dlx7e0.jsView on unpkg · L17Source contains an obfuscated payload loader that reconstructs and executes hidden code.
assets/AiPage-BnBgcdyY-59094c2b.jsView on unpkg · L1Source file is highly similar to a previously finalized malicious package; route for source-aware review.
assets/fingerprint-Y5nV5FVa-59094c2b.jsView on unpkgFindings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.59.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.59 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.