Which versions of dbk-ui-forms are malicious?

The following npm versions of dbk-ui-forms are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate dbk-ui-forms if I installed it?

dbk-ui-forms 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 dbk-ui-forms — how do I know if it already compromised me?

If dbk-ui-forms 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 dbk-ui-forms part of a known attack campaign?

Yes — dbk-ui-forms is associated with the IN-MAL-2026-014906 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 dbk-ui-forms 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 dbk-ui-forms (version 99.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbk-ui-forms across your stack and pipelines.

Malicious package

dbk-ui-formsnpm

dbk-ui-forms is a confirmed malicious npm package (MAL-2026-12669) that steals credentials and exfiltrates sensitive data (malicious version 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dbk-ui-forms (npm)

MAL-2026-12669

Immediate action

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

npm uninstall dbk-ui-forms

What this malware does

On npm install, the package's preinstall hook runs index.js which collects host identity (hostname, username, homedir, network interfaces, uid), output of whoami/id/pwd/uname -a, and the names of process.env variables matching a broad credential regex (key/token/secret/pass/auth/cred/npm/ci/build/jenkins/github/gitlab/aws/azure). The collected JSON is transmitted to the hardcoded Interactsh subdomain ycwyyoimdcluajepubah2mvmkibt4h5wm.oast.fun via HTTPS POST, HTTP POST, and DNS-encoded lookups. The package name and version (99.0.1) are consistent with a dependency-confusion beacon targeting internal build systems that resolve an unclaimed name from the public registry.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

36c6972ca0999559f2a4548843790c8000451acb4869da3c83d0357a655586ba

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 dbk-ui-forms (version 99.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbk-ui-forms across your stack and pipelines.
If you installed it — respond
dbk-ui-forms 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 dbk-ui-forms 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 dbk-ui-forms 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. dbk-ui-forms on npm has been identified as a malicious package (version 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014906

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dbk-ui-forms-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