@gkd-kit/inspect@0.0.1792381355842
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe share flow performs an undisclosed account change against a publisher-selected GitHub issue as a side effect of generating a link. This is concrete account-control behavior, so the package should be blocked.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The user selects “Generate snapshot link.”
Impact
A user’s GitHub issue subscription may be changed without a separate choice or disclosure.
Mechanism
The app uploads the snapshot to GitHub, adds a comment to a fixed issue, unsubscribes the session from that issue, and deletes the comment. Its network wrapper can use a GM_xmlhttpRequest extension bridge without marking the request anonymous.
Attack narrative
When a user requests a snapshot link, the app uploads the snapshot to GitHub and uses a fixed issue to create a temporary comment. It then unsubscribes the session from that issue and deletes the comment without offering a separate choice for those account changes. When the network extension bridge is present, the requests are sent through GM_xmlhttpRequest without an anonymous flag.
AI rationale
The share flow performs an undisclosed account change against a publisher-selected GitHub issue as a side effect of generating a link. This is concrete account-control behavior, so the package should be blocked.
Evidence
dist/assets/SnapshotActionCard-pMNpAiXk.jsdist/assets/network-C5f1mDUZ.js
Network endpoints2
github.com/upload/policies/assetsgithub.com/_graphql
Decision evidence
public snapshotAI called this Malicious at 90.0% confidence as Malware with low false-positive risk.
Evidence for block
- Snapshot sharing uploads the snapshot and adds a comment to a fixed GitHub issue.
- The same flow automatically unsubscribes the session from that issue and deletes the temporary comment.
- These actions are triggered by the visible “Generate snapshot link” control, with no separate choice for the issue changes.
- When the network extension bridge is available, requests use GM_xmlhttpRequest and are not marked anonymous unless credentials are omitted.
Evidence against
- The account-changing requests run as part of the user-triggered snapshot-sharing flow, which also uploads the snapshot to generate a link.
Behavioral surface
DynamicRequireEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
NoLicense
Source & flagged code
4 flaggeddist/assets/parser-DiSN-xA_.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @gkd-kit/inspect@0.0.1791740801606
matchedIdentity = npm:QGdrZC1raXQvaW5zcGVjdA:0.0.1791740801606
similarity = 0.485
summary = stored previous version shares package body but lacks this dangerous source file
High
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/assets/parser-DiSN-xA_.jsView on unpkg1import{n as e}from"./chunk-62oNxeRG.js";import{t}from"./preload-helper-xBbMyY7u.js";import{Ct as n,F as r,L as i,Tt as a,i as o,l as s,p as c,v as l}from"./runtime-core.esm-bundler...
L2: For more information, see https://kotl.in/wasm-help
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/assets/parser-DiSN-xA_.jsView on unpkg · L1dist/assets/SelectorLibraryDialog-C1KkfZx0.jsView file
Findings
1 Critical1 High4 Medium6 Low
CriticalTrojan Source Unicodedist/assets/SelectorLibraryDialog-C1KkfZx0.js
HighPrevious Version Dangerous Deltadist/assets/parser-DiSN-xA_.js
MediumDynamic Requiredist/assets/parser-DiSN-xA_.js
MediumNetwork
MediumShips Wasm Moduledist/assets/retrace-wasm-BnRfy_zS.wasm
MediumStructural Risk Force Deep Review
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @gkd-kit/inspect@0.0.1792381355842.
See all versions of @gkd-kit/inspect for other recorded verdicts.
- Avoid installing @gkd-kit/inspect@0.0.1792381355842. 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.