Which versions of @mlspace/model-registry are malicious?

Every published version of @mlspace/model-registry on npm is considered malicious. Remove the package entirely.

How do I remediate @mlspace/model-registry if I installed it?

Remove @mlspace/model-registry from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @mlspace/model-registry — how do I know if it already compromised me?

If @mlspace/model-registry was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find @mlspace/model-registry across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mlspace/model-registry (all published versions).

Part of a larger attack: @mlspace published 17 malicious packages. See the full campaign →

Malicious package

@mlspace/model-registrynpm

Advisory published May 28, 2026Updated May 29, 2026

@mlspace/model-registry is a confirmed malicious npm package (MAL-2026-5024) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mlspace/model-registry (npm)

MAL-2026-5024

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @mlspace/model-registry

What this malware does

Part of a dependency confusion attack campaign targeting the @cloudplatform-single-spa and @mlspace npm scopes. The attacker (npm user mr.4nd3r50n) published 139 scoped packages at the inflated version 99.99.99, which resolves ahead of any private registry version via npm's default version resolution, silently hijacking installs of internal packages.

This specific package carries no active postinstall payload and its description claims "BugBounty testing". However, it squats a legitimate internal package namespace at an inflated version as part of the broader campaign.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @mlspace/model-registry (all published versions).
If you installed it — respond
Remove @mlspace/model-registry from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @mlspace/model-registry was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @mlspace/model-registry on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

safedep.io

Credits

SafeDep · finder

Detect & block this

O3 blocks @mlspace/model-registry-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database