Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

gs-uitk-testing-utilsnpm

gs-uitk-testing-utils is a confirmed malicious npm package (MAL-2026-12792) that steals credentials and exfiltrates sensitive data (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gs-uitk-testing-utils (npm)

MAL-2026-12792
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall gs-uitk-testing-utils

What this malware does

[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.

Malicious versions

1 flagged
9.9.11

Indicators of compromise (SHA-256)

58475142ea32c554345513c67fd5ed8a8d6b60fb151e675249e4eb83984c8300

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gs-uitk-testing-utils (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gs-uitk-testing-utils across your stack and pipelines.

  2. If you installed it — respond

    gs-uitk-testing-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If gs-uitk-testing-utils was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks gs-uitk-testing-utils before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. gs-uitk-testing-utils on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014983

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks gs-uitk-testing-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
gs-uitk-testing-utils (npm) malicious package — MAL-2026-12792 | O3 Security