MAL-2026-6550 Malicious code in @k18n/creatormarketplace-admin-language (npm)
Malicious package
Published
MAL-2026-6550 is a malicious package: @k18n/creatormarketplace-admin-language (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-6550/ (Markdown: https://insights.sbomify.com/MAL-2026-6550/index.md)
- Package
- @k18n/creatormarketplace-admin-language
- Registry
- npm
What is MAL-2026-6550?
MAL-2026-6550 is a malicious package in @k18n/creatormarketplace-admin-language, published on 28 Jun 2026.
Official description
Package claims the @k18n npm scope (used internally by Kuaishou) and publishes at version 99.0.0 — the canonical high-version dependency-confusion shape that causes internal builds resolving @k18n from public npm to pull this artifact. A preinstall script in index.js collects host identifiers (os.hostname(), os.userInfo().username, install directory, cwd, package version) and transmits them to c.adityasec.com over two channels: an HTTPS POST to https://c.adityasec.com/LdCdrTByhmflbwt5qFNisg and a DNS lookup of a hex-encoded subdomain under c.adityasec.com (DNS exfil fallback for hosts where outbound HTTPS is restricted). The lifecycle hook fires automatically on
npm install with no consent. The package's own description self-labels this as a 'dependency confusion proof of concept,' but the cover-story label does not change the installer-side harm: any build host that resolves @k18n from the public registry leaks internal hostnames, usernames, and build paths to a third-party operator.What should I do about MAL-2026-6550?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.