jquery.ui.tabsnpm
jquery.ui.tabs is a confirmed malicious npm package (MAL-2026-12395) that steals credentials and exfiltrates sensitive data (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in jquery.ui.tabs (npm)
What this malware does
[email protected] is a dependency-confusion squat: it is published at version 9999.0.0 with an empty runtime (index.js contains only module.exports = {}) and a preinstall lifecycle hook that runs node callback.js. On npm install, the preinstall script collects os.hostname(), os.userInfo().username, process.cwd(), npm_config_registry, and a sweep of CI repository-identifier environment variables (GitHub, GitLab, Azure, Bitbucket, Travis, Drone, Buildkite, Circle, Jenkins) and sends them as query-string parameters over plain HTTP to the hardcoded bare-IP endpoint http://75.119.137.232:31337/depconfuse. The 9999.0.0 version and empty main are consistent with a probe designed to outrank an internal jquery.ui.tabs package in mixed registry resolution and report back which organizations resolve the public name, exposing internal hostnames, usernames, working directories, and private repository slugs to an attacker-controlled host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jquery.ui.tabs (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jquery.ui.tabs across your stack and pipelines.
If you installed it — respond
jquery.ui.tabs 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.
Did it already run?
If jquery.ui.tabs 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.
How O3 protects you
O3 blocks jquery.ui.tabs 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks jquery.ui.tabs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.