OK, I figured it out. I was bundling a file in the package that didn't have an extension, and NuGet was putting an entry in the [Content_Types].xml file that looked like
<Default ContentType="application/octet" Extension=""/>
This looks like a bug in NuGet. At the very least, if extension-less files are invalid in a nupkg, NuGet should error out during packaging.