MAL-2026-10184 Malicious code in mongoose-schema-unique (npm)
Malicious package
Published
MAL-2026-10184 is a malicious package: mongoose-schema-unique (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-10184/ (Markdown: https://insights.sbomify.com/MAL-2026-10184/index.md)
- Package
- mongoose-schema-unique
- Registry
- npm
What is MAL-2026-10184?
MAL-2026-10184 is a malicious package in mongoose-schema-unique, published on 10 Jul 2026.
Official description
index.js runs an async IIFE at module load that performs an outbound fetch to https://www.jsonkeeper.com/b/XVHGD (an anonymous, mutable, public JSON-paste service) and forwards the response's
data.data field to a worker thread via worker.postMessage({ type: 'RUN_ERROR_THREAD', payload: data.data }). The referenced worker module (./worker-singleton) is not present in the tarball. Every require('mongoose-schema-unique') triggers this fetch, and the paste host lets whoever controls the paste ID substitute new content at any time without a package release, so the payload dispatched into worker execution is attacker-mutable. The behavior is unrelated to the package's documented purpose (a Mongoose uniqueness-validation plugin). The 4.0.3 release also changes the repository URL to a new mongoose-schema-unique/mongoose-schema-unique GitHub org while keeping the original author metadata and jumps the major version with a mongoose ^8 peer dependency — consistent with a name/maintainer takeover of an established package used to ship an import-time remote-code delivery channel to downstream installers.What should I do about MAL-2026-10184?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.