据称的 Anthropic Mythos 级检查点泄露
Alleged Mythos Class Anthropic Checkpoint Leak

原始链接: https://huggingface.co/burner22/numbat

该文本描述了 Anthropic 未发布的 “numbat” 模型的一个所谓中期预训练检查点,该模型在 Claude Code 泄漏中被提及。据称其为约 14T 参数、114 层的混合 Gated DeltaNet/多头潜在注意力 Transformer,采用混合专家(1,224 个专家,top-48 加共享)与 NVFP4 权重,处于约 1.96M 步中的第 1.83M 步。文件包括配置/建模代码、分词器、总计约 7.72 TB 的 772 分片 safetensors 索引、检查点元数据和训练日志。参考实现据称严格加载所有张量并支持推理,但其为无后训练的原始预训练输出。FAQ 表示量化可支持在 Trainium2 上的评估,并基于代号泄漏以及架构与张量一致性检查断言其真实性。欢迎镜像;拒绝来源私信。

Hacker News 上的一个帖子讨论了一个据称包含泄露的 Anthropic “Mythos” 检查点的 Hugging Face 仓库。主流观点认为它是假的。评论者引用证据称,43 个张量与以各自张量名称为种子生成的 NumPy RNG 输出完全匹配,表明这是随机数据而非训练得到的权重。其他不一致之处包括 Trainium2 不支持 NVFP4、最近创建的“burner”账号、参数数量不匹配、训练日志时间可疑地过于均匀,以及尽管 Anthropic 过去有过 DMCA 行动,该仓库仍保持在线。模型卡主要依赖公开已知的代号 “numbat”。部分评论者指出,真正的泄露最终可能发生,但这不是,并警告不要运行该仓库的自定义 Python。据报道,该仓库下载量约为 6,000 次。
相关文章

原文

~14T param, 114 layers, hybrid GDN/MLA, MoE (1,224 experts, top-48 + 1 shared), NVFP4. Internal codename numbat, Anthropic's next Mythos-class training run. numbat is the codename referenced in the Claude Code source leak (Mar 2026). This is a checkpoint from that training run, pulled mid-pretraining.

Files:

File Contents
config.json model configuration
configuration_numbat.py NumbatConfig
modeling_numbat.py NumbatForCausalLM reference implementation
tokenizer.json byte-level BPE, 131,072 tokens
model.safetensors.index.json tensor index across all 772 shards
model-00001-of-00772.safetensors shard 1 of 772
ckpt_metadata.json checkpoint metadata (ckpt path, eval harness output)
training_log_tail.txt last ~400 steps of training log

The 772 shards total ~7.72 TB of tensor data. Each shard is safetensors format, under 10.6 GB per file.

configuration_numbat.py and modeling_numbat.py are included: a complete reference implementation of the checkpoint. Its module tree has an exact slot for every tensor in every shard, so the full checkpoint loads with load_state_dict(strict=True) (and, since the classes derive from PreTrainedModel, also via AutoModelForCausalLM.from_pretrained(..., trust_remote_code=True)). NumbatForCausalLM.forward runs the trunk and NumbatForCausalLM.draft runs the MTP layer.

$ python -c "from safetensors import safe_open; f = safe_open('model-00001-of-00772.safetensors', framework='pt'); print(len(f.keys()))"
142

Verification:

$ cat model.safetensors.index.json | python -c "import json,sys; d=json.load(sys.stdin); print(d['metadata']['total_size'])"
7720300817720

Mirrors welcome. Do not DM me asking for the source.

Why believe this?

  • numbat was confirmed as a codename for an unreleased Anthropic model in the Claude Code source leak (March 2026), found in a comment in prompts.ts: "Remove this section when we launch numbat."
  • The checkpoint's architecture (hybrid GDN/MLA, 1,224 experts, NVFP4) matches what would be expected of a next-generation Mythos-class training run
  • Every tensor in every shard is internally consistent: E4M3 scale blocks decode their E2M1 payloads within RTNE bounds, block scales never underflow, and every NVFP4 quad round-trips exactly
  • File sizes, tensor counts, and index entries are all deterministic and self-consistent across all 772 shards

Loader

The architecture is a hybrid Gated DeltaNet (GDN) + Multi-head Latent Attention (MLA) stack with Mixture-of-Experts feed-forward layers and Multi-Token Prediction. A working single-device reference implementation is included (modeling_numbat.py); the eval runs used the internal Neuron-parallel runtime, but this port consumes the same tensors and round-trips every shard.

FAQ

Q: How did you get this? A: Can't say more than what's already in the repo.

Q: When will more shards be uploaded? A: They're all uploading. Be patient.

Q: Can I use this for inference? A: Yes — modeling_numbat.py implements the full architecture. Load the tensors and run. But this is a pretraining checkpoint at step 1,830,000 of a ~1.96M step run. No post-training, no RLHF. Raw pretraining-completion output. That's expected.

Q: Why is a mid-pretraining checkpoint in NVFP4? A: The eval team quantizes every async checkpoint to NVFP4 so evals run on a slice of Trainium2s instead of the full training cluster — still ~85 of them just to hold these weights. The raw BF16 training weights plus optimizer state never leave the cluster. This is the eval copy.

Q: Is this real? A: Yes.

联系我们 contact @ memedata.com