@lucideproxy/svg@0.0.69
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source establishes a high-risk browser proxy capability and opaque runtime behavior, but not a concrete npm install-time attack or proven theft endpoint. It should be warned rather than blocked.
Decision evidence
public snapshot- The package is a browser proxy bundle despite its SVG-oriented package name.
- Opening the bundled site registers a service worker automatically.
- The worker intercepts routed browser requests and forwards request URLs, headers, and bodies to a controller.
- Large application bundles are deliberately obfuscated, including a dynamic Function constructor.
- This creates a credential and browsing-data exposure capability without any npm install-time hook.
- package.json contains no lifecycle scripts, dependencies, executable entry point, or self-dependency.
- No Node file, environment, shell, or install-time behavior was found.
- The manifest describes the artifact as a static proxy-site bundle, consistent with the browser code.
Source & flagged code
5 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-225af2ca.jsView on unpkg · L13Package source references dynamic require/import behavior.
4wv2l/p2fs4c.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.69.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.69 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.