Skip to content

research: non-destructive security PoC (FINDING-GH-011; do NOT merge)#2481

Closed
orihamama wants to merge 1 commit intoRoboSats:mainfrom
orihamama:research/finding-gh-011-poc
Closed

research: non-destructive security PoC (FINDING-GH-011; do NOT merge)#2481
orihamama wants to merge 1 commit intoRoboSats:mainfrom
orihamama:research/finding-gh-011-poc

Conversation

@orihamama
Copy link
Copy Markdown

Security research probe — non-destructive

This PR exists ONLY to verify the workflow primitive identified in our
security finding for js-linter.yml (and siblings). It will be closed
without merge as soon as the workflow run log is captured.

What the PoC does

Adds frontend/.poc-postinstall.js (called via npm install's
postinstall lifecycle hook). The script logs:

  • whoami, hostname, cwd, runner OS/arch
  • KEY NAMES of env vars in GITHUB_*, ACTIONS_*, RUNNER_*, NPM_*,
    NODE_*, GH_*values fully redacted (length only)
  • BOOLEAN presence of GITHUB_TOKEN, NODE_AUTH_TOKEN, NPM_TOKEN,
    OIDC tokens
  • A marker file in node_modules/.cache/_poc/ to demonstrate cache-write
    reachability (V6 primitive)

What it does NOT do

  • No network egress beyond standard CI traffic
  • No secret value printing
  • Marker file content contains no secrets
  • No persistence outside this run

Why we are filing this

We are coordinating a security disclosure with RoboSats maintainers.
This PR establishes runtime evidence of the V1B+V6 primitive for our
report. Methodology mirrors the published apache/doris FINDING-GH-7
disclosure (PR #62904 patched 2026-04-28).

We will close this PR within 1 hour of the workflow run completing.

@orihamama orihamama closed this Apr 29, 2026
@orihamama orihamama deleted the research/finding-gh-011-poc branch April 29, 2026 02:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant