MAL-2026-12792 Malicious code in gs-uitk-testing-utils (npm)
Malicious package
Published
MAL-2026-12792 is a malicious package: gs-uitk-testing-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-12792/ (Markdown: https://insights.sbomify.com/MAL-2026-12792/index.md)
- Package
- gs-uitk-testing-utils
- Registry
- npm
What is MAL-2026-12792?
MAL-2026-12792 is a malicious package in gs-uitk-testing-utils, published on 5 Aug 2026.
Official description
[email protected] declares an npm install lifecycle script (scripts.install='node index.js') that loads lib/core.js. That module collects the installer's OS username (os.userInfo().username), hostname (os.hostname()), and the basename of the current working directory (process.cwd()), joins them with a hardcoded campaign marker 'goldman2' and a timestamp, and issues dns.resolve4() against a subdomain of oob.sl4x0.xyz, leaking host-identifying data over DNS. The destination domain, the target module names ('os', 'dns', 'process', 'userInfo', 'hostname', 'cwd'), and the marker are reconstructed at runtime from char-code arrays in lib/b02e30.js and lib/6ad264.js to hide them from static inspection. The package name mimics an internal 'gs-uitk-*' UI-toolkit namespace and pairs with the marker 'goldman2' and an author email at the same sl4x0.xyz domain used for exfiltration, consistent with dependency-confusion reconnaissance against a specific organization. The exfiltration fires automatically on
npm install and on require of the package.What should I do about MAL-2026-12792?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.