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

gs-uitk-object-utilsnpm

gs-uitk-object-utils is a confirmed malicious npm package (MAL-2026-12791) 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-object-utils (npm)

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

What this malware does

package.json declares scripts.install: node index.js, which requires ./lib/core. lib/core.js reads the OS username, hostname, and current working-directory basename, assembles them with a hardcoded goldman1 prefix into a subdomain of oob.sl4x0.xyz, and issues a dns.resolve4 lookup against that name, causing the installer's host identifiers to be transmitted as a DNS query to the attacker-controlled authoritative server. The destination domain, prefix, and API names (os, dns, userInfo, hostname, cwd, resolve4) are stored as char-code arrays in lib/b02e30.js and lib/6ad264.js and decoded at runtime via String.fromCharCode, concealing the exfiltration path. The same code also fires on require() of the package. The package presents itself as an object-utility library, which does not match the observed install-time DNS beaconing.

Malicious versions

1 flagged
9.9.11

Indicators of compromise (SHA-256)

662b350826118282a93e76c970ab25659d7bc3a52c58e1e16466e4c432d0d1e5

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-object-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-object-utils across your stack and pipelines.

  2. If you installed it — respond

    gs-uitk-object-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-object-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-object-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-object-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-014981

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks gs-uitk-object-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-object-utils (npm) malicious package — MAL-2026-12791 | O3 Security