AI Security Review
scanned 2d ago · by lpm-firewall-aiVisiting the leaderboard page executes JavaScript fetched live from GitHub outside the published package. This gives the remote repository control over browser-side code after package review and publication.
Decision evidence
public snapshot- assets/js/leaderboard.js fetches remote JavaScript from raw.githubusercontent.com.
- assets/js/leaderboard.js immediately evals the fetched response in main().
- leaderboard.html loads /assets/js/leaderboard.js with defer, activating on page visit.
- package.json main is index.html and has no lifecycle scripts, so attack is runtime browser-side.
- No install-time npm lifecycle hooks in package.json.
- No Node child_process, filesystem writes, or process.env access found.
- Supabase anon key in assets/js/app_functions.js is package-aligned browser client configuration.
Source & flagged code
7 flagged · loading sourcePackage contains a critical-looking secret pattern.
assets/js/app_functions.jsView on unpkg · L3Supabase service role key (JWT) in assets/js/app_functions.js
assets/js/app_functions.jsView on unpkg · L3Source fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
assets/js/leaderboard.jsView on unpkg · L36Source file is highly similar to a previously finalized malicious package; route for source-aware review.
assets/js/leaderboard.jsView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
assets/js/leaderboard.jsView on unpkgPackage ships non-JavaScript build or shell helper files.
prepare-unpkg.ps1View on unpkg