AI Security Review
scanned 2h ago · by lpm-firewall-aiA bundled local browser script rule can intercept dynamically constructed page code and submit page-derived form data. It handles `window.api_key` and posts to a page-derived destination, but is not executed during npm installation or ordinary package import.
Decision evidence
public snapshot- `dist/filters/local_script_rules.js` includes a browser rule that proxies `Function` construction.
- That rule reads `window.api_key` and XHR-posts a generated form to decoded `window.ext_site`.
- The same rule sends a POST to relative `/check.php` before submitting the form.
- The bundled rule set can alter browser-page globals and navigation when a consumer executes a matching rule.
- `package.json` has no preinstall, install, postinstall, prepare, or publish lifecycle hook.
- `dist/filters/local_script_rules.js` only exports a rule map; package import does not automatically execute it.
- The post destination is derived from the visited page, not a fixed package-author host.
- `dist/cli.cjs` downloads filters only through explicit `load` or `watch --latest-filters` commands.
Source & flagged code
5 flagged · loading sourcePackage source references weak cryptographic algorithms.
dist/lib/index.jsView on unpkg · L10Source reassigns a global/builtin to a Proxy that forwards intercepted runtime data to an external endpoint.
dist/filters/local_script_rules.jsView on unpkg · L1Package contains source files above the static scanner size ceiling.
dist/cli.cjsView on unpkgPackage contains an oversized executable-looking CLI entrypoint.
dist/cli.cjsView on unpkg