The issue has been resolved, and all affected services are operating normally.

We identified a caching issue affecting metadata responses for some npm packages served through Secure Registry. Affected responses may contain package download URLs pointing to a different registry endpoint than the one configured by the customer. This may cause package installation or dependency resolution failures.
The issue occurs when registry deployments share cached metadata containing deployment-specific download URLs. We have identified the root cause and are preparing a fix to isolate these cached responses by registry endpoint.