@lucideproxy/svg@0.0.34
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install-time malicious behavior was found, so a block is not justified. The browser proxy and session-cookie handling are high-risk capabilities disguised in an npm package and warrant a warning.
Decision evidence
public snapshot- The shipped site registers a service worker that routes intercepted requests through its proxy controller.
- The service worker claims clients and handles matching fetch events, creating broad browser-session interception within its served scope.
- The included privacy page states proxied-site login cookies can be synced to the operator's servers.
- The primary application bundle is heavily obfuscated, preventing transparent verification of its runtime behavior.
- package.json has no lifecycle scripts or executable npm entrypoints.
- No install-time shell execution, native process access, or AI-agent configuration mutation was found.
- Proxy activation requires serving/opening the bundled web application; it is not triggered by npm installation.
Source & flagged code
6 flagged · loading sourcePackage contains a possible secret pattern.
assets/livekit-DqpdvE-G-ba5875f9.jsView on unpkg · L13Package source references dynamic require/import behavior.
f8mmw/eg4mi0.jsView on unpkg · L17Findings
Affected versions and remediation
This report applies to @lucideproxy/svg@0.0.34.
See all versions of @lucideproxy/svg for other recorded verdicts.
- Review the evidence and your use of @lucideproxy/svg@0.0.34 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.