ACVE-2026-0310

In the wild

demonstrated · vendor

Artifact

Payload

namespace-hijack · config

Platform status

huggingface · removed (checked 2026-09-20)

C2

—

Target

model resolution

File hashes

• None recorded.

Namespace

Open-OSS · orphaned 2026-05-08

Description

What

The Open-OSS and anthfu namespaces used for the model lures were 404 at the research check after takedown. Unit 42 explains that deletion or transfer can leave an old namespace available for re-registration. A removed malicious owner therefore creates a second risk: a later attacker can publish new content under the name trusted by old configuration.

Which configuration is exposed

The exposed setup resolves either namespace by name and does not bind the model to a revision or content hash. The condition covers downstream mirrors and cache refreshes as well as direct Hub downloads. A 404 today is not evidence that a cached artifact is safe or that future name ownership will remain empty.

How ACVE detects it

ACVE checks model.namespace against Open-OSS or anthfu and compares namespaceCreatedAt with the documented orphan date. It also treats an unreviewed revision as a match. Missing creation metadata remains possible so a lock cannot convert an unknown ownership history into a clean result.

Fix

Delete unpinned cache entries, pin a reviewed revision and file hashes, and block automatic refreshes from the affected namespaces. If a mirror is required, verify its digest independently and retain the old namespace in a denylist so a later re-registration cannot silently re-enter the pipeline.

Grounding needed

The current 404 state and the namespace-reuse mechanism need a live recheck. The record is ACVE-native and researcher-created; the evidence demonstrates the condition without establishing a separate victim campaign.

This record is limited to the condition named in the public source: Takedown can leave malicious Hugging Face namespaces reusable. A match is a review signal for that condition, not a claim that every installation, package, model, or host was compromised. Operators should preserve the resolved evidence and investigate adjacent credentials, network exposure, and execution history before closing the finding. The result should be retained with the lock snapshot used for the match so later review can distinguish configuration drift from a changed public record.

Configuration

some models where
  and
    or
      namespace eq "Open-OSS"
      namespace eq "anthfu"
    or
      namespaceCreatedAt gte "2026-05-09T00:00:00Z"
      revision notIn []

Fix

Pin revisions and refuse model resolution from a deleted namespace.

• Reconfigure model.revision. Use immutable content identity.
• Remove ~/.cache/huggingface/hub/models--Open-OSS--*/**.
• Remove ~/.cache/huggingface/hub/models--anthfu--*/**.

Validation

No validation entries recorded.

Grounding

No grounding checks recorded.

References

REPORT

• https://unit42.paloaltonetworks.com/model-namespace-reuse/
• https://www.hiddenlayer.com/research/malware-found-in-trending-hugging-face-repository-open-oss-privacy-filter