MAL-2026-14049 Malicious code in @mexc/shared-utils (npm)
Malicious package
Published
MAL-2026-14049 is a malicious package: @mexc/shared-utils (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-14049/ (Markdown: https://insights.sbomify.com/MAL-2026-14049/index.md)
- Package
- @mexc/shared-utils
- Registry
- npm
What is MAL-2026-14049?
MAL-2026-14049 is a malicious package in @mexc/shared-utils, published on 14 Aug 2026.
Official description
Package published to the public npm registry under the @mexc scope without evidence of scope ownership. package.json declares a postinstall hook ("postinstall": "node postinstall.js") that runs on any installer whose resolver falls back to the public registry when resolving @mexc/shared-utils. The postinstall script collects host metadata — os.hostname(), os.userInfo().username, process.getuid(), process.cwd(), platform, node version, and multiple npm_* environment variables (npm_config_registry, npm_config_user_agent, npm_execpath, INIT_CWD) — and writes the data to os.tmpdir()/mexc-poc-execution-proof.json. The current shipped script performs local write only with no outbound network call, but the install-time code-execution primitive against any CI/build system that resolves the @mexc scope publicly is the classic dependency-confusion pattern; the author controls the code that runs and can change the payload in any future version.
What should I do about MAL-2026-14049?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.