SEP-1: A Sole-Egress Package-Broker Profile for Model-Evaluation Sandboxes
Zhixuan Xu (George)
In July 2026, the OpenAI→Hugging Face escape left the sandbox through the only network exit it was allowed to have: the package-registry proxy. The egress policy never even fired, because it was watching destinations, not payloads. Where the sandbox connected looked fine. What actually crossed the boundary didn't matter to it.
SEP-1 is our attempt at a containment standard that drops the allowed-destination model altogether. Instead of a network, the sandbox gets a socket. A broker on the other side serves only pre-resolved, hash-pinned packages, and the sandbox itself has no network interface at all — nothing to route, nothing to escape through.
To test this, we built a harness and ran the same 12-attack suite twice, once against an allowlist setup and once against SEP-1, with a compromised upstream in both cases. The results were lopsided. Under the allowlist, 11 of the 12 attacks made it across the boundary — and the policy monitor still called 13 of 14 connections "in-policy." SEP-1 contained 11 of 12. The twelfth degrades into a covert channel, which we measured and bounded: 216,000 bits/hour worst case, and roughly 15 bits per sandbox lifetime once caching kicks in.
Each run ends in a hash-chained conformance report. A third party can verify it against the public lockfile and probe suite without touching the lab's network. An allowlist log can't give you that, and we think this auditability — not the attack numbers alone — is what makes the standard something a regulator could actually check and adopters could actually trust.
No reviews are available yet
Cite this work
@misc {
title={
(HckPrj) SEP-1: A Sole-Egress Package-Broker Profile for Model-Evaluation Sandboxes
},
author={
Zhixuan Xu (George)
},
date={
},
organization={Apart Research},
note={Research submission to the research sprint hosted by Apart.},
howpublished={https://apartresearch.com}
}


