Which versions of unifi-credential-server are malicious?

The following npm versions of unifi-credential-server are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate unifi-credential-server if I installed it?

unifi-credential-server 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.

I already installed unifi-credential-server — how do I know if it already compromised me?

If unifi-credential-server 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.

Is unifi-credential-server part of a known attack campaign?

Yes — unifi-credential-server is associated with the RLMA-2026-06532, IN-MAL-2026-019734 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find unifi-credential-server across my projects, lockfiles, and CI pipelines?

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

Malicious package

unifi-credential-servernpm

unifi-credential-server is a confirmed malicious npm package (MAL-2026-15692) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in unifi-credential-server (npm)

MAL-2026-15692

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall unifi-credential-server

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. index.js collects hostname, username, working directory, internal IPv4 addresses from os.networkInterfaces(), and CI/build environment variables (GITHUB_REPOSITORY, GITHUB_RUN_ID, GITLAB_CI, npm_config_registry, npm_package_name, AWS_REGION, JENKINS_URL, and others), hex-encodes the payload into <=60-character DNS labels appended to the hardcoded base domain d8hjn6ap4rntta9vj5ve0jkl1seb4k3kci.oast.me, and exfiltrates via dns.resolve() of the constructed FQDN plus an https.get() to the same host. A secondary DNS query using the package name as a subdomain is also emitted. The name unifi-credential-server and version 99.0.0 are consistent with a dependency-confusion lure targeting internal builds that resolve the name against the public registry.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

bc68e1524fd4839280cd5e9e509a6ed3a8693189e9f912930cb5b957dea45360

6c9d5fc3394d6f2565267e1b19573ca0c58dbbe9149f7204ea39ccae5c53645f

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for unifi-credential-server (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unifi-credential-server across your stack and pipelines.
If you installed it — respond
unifi-credential-server 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 unifi-credential-server 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 unifi-credential-server 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. unifi-credential-server on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-06532IN-MAL-2026-019734

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks unifi-credential-server-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