@lucideproxy/svg@0.0.32
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a browser proxy and persistent service-worker control surface inconsistent with an SVG package. Its obfuscation and fingerprinting warrant a warning, but the inspected source does not meet the concrete-attack threshold for blocking.
Decision evidence
public snapshot- The package is a browser proxy bundle, not an SVG library.
- Browser runtime registers a service worker and configures a proxy controller with WASM and injected worker code.
- The worker routes matching fetches and the controller persists proxy cookies in IndexedDB.
- AI-page code is deliberately obfuscated and sends a fingerprint header.
- package.json has no lifecycle scripts, bin, main, or exports entrypoint.
- No Node filesystem, child-process, environment harvesting, or install-time execution was found.
- No fixed credential-exfiltration endpoint or concrete payload execution chain was confirmed.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-7f2de5e0.jsView on unpkg · L13Package source references dynamic require/import behavior.
rqbm5/pnbgq4.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.32.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.32 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.