@mlspace/model-registrynpm
Malicious code in @mlspace/model-registry (npm) Remove it immediately and rotate any exposed credentials.
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
Every published version of this package is considered malicious — remove it entirely.
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mlspace/model-registry (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mlspace/model-registry across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @mlspace/model-registry before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
References
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.