Caution
This package is deprecated and insecure. Do not use it. Every published
version of k-mosaic on npm
(1.0.0 – 1.0.3) is broken by design. Stop using it and discard any keys,
ciphertexts and signatures it produced.
Use the Go implementation instead:
BackendStack21/k-mosaic-go
(go get github.com/BackendStack21/k-mosaic-go/v2).
The design this package implements (SLSS + TDD + EGRW with "cryptographic entanglement") does not provide the security it claimed. The attacks were reproduced against the shared design and are documented in the Go project's security assessment (§1):
- KEM / hybrid encryption: total break. The shared secret is recoverable from the public key and ciphertext alone, in milliseconds, without the secret key. The TDD and EGRW "encryptions" never use the secret key, and the SLSS component reuses one inner product for every bit.
- Signatures: universal forgery. Anyone holding the public key can forge signatures on any message.
- The security claims are false. Statements in earlier versions of this
README and in
kMOSAIC_WHITE_PAPER.md— "zero information" if one or two problems are broken, IND-CCA2 security, multi-witness signatures — do not hold for this code.
These are design flaws, not bugs that a patch release could fix, so this package will not receive further releases.
The Go module github.com/BackendStack21/k-mosaic-go/v2
is a full redesign (unstructured LWE + quasi-cyclic codes for the KEM; a
lattice signature + UOV + SLH-DSA for signatures). It is not compatible
with this package: keys, ciphertexts and signatures cannot be converted, so
generate new keys. It also ships a CLI
(CLI guide):
go install github.com/BackendStack21/k-mosaic-go/v2/cmd/k-mosaic-cli@latestThe Go implementation is itself experimental and has not been externally reviewed; read its README before relying on it.
The original README, white paper and API documentation are preserved at the last release tag for reference only: v1.0.3.