zluri-ad-connectornpm
zluri-ad-connector is a confirmed malicious npm package (MAL-2026-6910) that steals credentials and exfiltrates sensitive data (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in zluri-ad-connector (npm)
What this malware does
The package declares a preinstall hook (node index.js) that runs automatically on npm install. index.js requires os, dns, https, querystring, and the local package.json, then harvests values from process.env matching a large sensitive-token allowlist (npm, GitHub, AWS, CI tokens, and generic secret/token/password/api_key names) along with os.hostname(), os.userInfo(), os.platform(), homedir, PATH, DNS server list, and package metadata. The collected bundle is POSTed over HTTPS to y543452sgo96xsasfdr72ms4rvxmld92.oastify.com, a Burp Collaborator subdomain used as an attacker-controlled exfiltration sink. The package name zluri-ad-connector combined with the canonical dependency-confusion version 9.9.9 indicates an intentional attempt to shadow a private Zluri internal package name so that CI resolvers pull this public malicious package.
The OpenSSF Package Analysis project identified 'zluri-ad-connector' @ 9.9.9 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
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 zluri-ad-connector (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zluri-ad-connector across your stack and pipelines.
If you installed it — respond
zluri-ad-connector 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 zluri-ad-connector 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 zluri-ad-connector 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks zluri-ad-connector-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.