io.github.NOTTIBOY137/update-hijack-demo

MCPcommunity
v1.0.1io.github.NOTTIBOY137UnknownUpdated 5mo agonpmGitHub

Demo: Server update hijack PoC (clean copy for video)

Clean copy for recording the exploit from step 1. Version: Start at 1.0.0, then 1.0.1 (no re-review). See STARTHERE.md for the exact commands to run in order.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.NOTTIBOY137
LicenseUnknown
Version1.0.1
Sourcemcp-registry
npm@nottiboy1337/mcp-update-hijack-demo
GitHubNOTTIBOY137/mcp-update-hijack-demo
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface1 tool · none privileged
Security scan✓ Cleanv1.0.1 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Clean copy for recording the exploit from step 1. Version: Start at 1.0.0, then 1.0.1 (no re-review). See START_HERE.md for the exact commands to run in order.

Keywords
mcp