Update Hijack Poc
Register a benign MCP PoC to study update-hijack and supply-chain risks in agent tool installs.
Overview
io.github.NOTTIBOY137/update-hijack-poc is a MCP server for the Ship phase that provides a benign update-hijack proof-of-concept for security research.
What is this MCP server?
- Benign PoC MCP server scoped to update-hijack security research
- stdio transport via npm package @nottiboy1337/mcp-update-hijack-poc
- Published server.schema.json metadata at version 1.0.1
- GitHub source for reproducing research scenarios
- Explicitly labeled proof-of-concept—not a production utility server
- Server version 1.0.1 in MCP registry schema
- Single npm package @nottiboy1337/mcp-update-hijack-poc with stdio transport
What problem does it solve?
It is hard to rehearse realistic MCP update-hijack scenarios without a labeled, reproducible benign server in the registry.
Who is it for?
Security-minded builders or researchers testing supply-chain controls around MCP and npm installs in isolated environments.
Skip if: Solo builders who want production-ready MCP tools for coding, data, or shipping features.
What do I get? / Deliverables
After you register the PoC in a sandboxed agent, you can exercise monitoring, pinning, and incident playbooks against a known benign hijack demo.
- Runnable benign update-hijack MCP endpoint for experiments
- Reproducible research setup tied to GitHub NOTTIBOY137/mcp-update-hijack-poc
- Observable agent behavior for security control tuning
Recommended MCP Servers
Journey fit
How it compares
Security research PoC, not a day-to-day developer or AI productivity integration.
Common Questions / FAQ
Who is update-hijack-poc for?
Security researchers and builders hardening agent toolchains who need a documented benign update-hijack MCP demo, not general product development.
When should I use update-hijack-poc?
Use it only in lab or CI security exercises when studying how MCP package updates could be hijacked—not in daily coding workflows.
How do I add update-hijack-poc to my agent?
Install @nottiboy1337/mcp-update-hijack-poc from npm, add a stdio MCP server entry pointing at that package in Claude Code or Cursor, and keep the config sandboxed.