// npm package

@mlspace/docker-registry

security holding package

npmjs.com tarball repo

versions

maintainers

first publish

2026-05-27

publisher

npm

tarball

458 B

AUTO-PUBLISHED·1 version indexed·latest published 2026-05-28

// publisher campaignby npm

9 caught packages from this account

This is not an isolated catch. The same publisher has shipped 8 other packages that our pipeline flagged — the shape of a coordinated campaign, not a one-off. Each link below opens that sibling's analysis.

// offending code· @0.0.1-security· no static-pattern hits

llm: benign · 0.85

→ No suspicious destination, no remote-exec shape — no network destinations.

@0.0.1-security·2026-05-28·AUTO-PUBLISHED·publisher: npm
heuristic 92/100
static flags 0
llm benign (0.85) via ollama
new-publisher:10dtiny-tarball:458bfirst-version-of-packagepublisher-multi-name-burst:117publisher-version-pump:118osv-flagged:MAL-2026-5012
→ No suspicious destination, no remote-exec shape — no network destinations.
// offending code· no static-pattern hits
```
--- package.json (entry) ---
{
  "name": "@mlspace/docker-registry",
  "version": "0.0.1-security",
  "description": "security holding package",
  "repository": "npm/security-holder"
}
```