MAL-2026-14206 Malicious code in @sarex-team/ui-kit (npm)
Malicious package
Published
MAL-2026-14206 is a malicious package: @sarex-team/ui-kit (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-14206/ (Markdown: https://insights.sbomify.com/MAL-2026-14206/index.md)
- Package
- @sarex-team/ui-kit
- Registry
- npm
What is MAL-2026-14206?
MAL-2026-14206 is a malicious package in @sarex-team/ui-kit, published on 19 Aug 2026.
Official description
@sarex-team/ui-kit runs a DNS-based out-of-band exfiltration beacon on both
npm install (via package.json scripts.install = node index.js) and on require('@sarex-team/ui-kit') (top-level require of lib/core.js from index.js, wrapped in silent try/catch). lib/core.js collects the installer's OS username, hostname, and current working-directory basename and issues a dns.resolve4 lookup against a subdomain of oob.sl4x0.xyz built from those values, leaking host identity through DNS. The sensitive API names ('os', 'dns', 'process', 'userInfo', 'username', 'hostname', 'cwd', 'resolve4') and the destination domain 'oob.sl4x0.xyz' are reconstructed at runtime from hex char-code arrays in lib/b02e30.js and lib/6ad264.js (obfuscator.io-style _0x-prefixed identifiers) to evade static detection. The package presents itself as 'Enterprise-grade utilities' with decoy validation/formatting/network/crypto/async modules under src/, and its homepage/repo URL github.com/slaxorg/@sarex-team/ui-kit is malformed and does not resolve to a real repository. The author email [email protected] matches the exfiltration domain sl4x0.xyz.What should I do about MAL-2026-14206?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.