Which versions of smb-portal-uikit are malicious?

The following npm versions of smb-portal-uikit are flagged malicious: 18.1.1. Treat any of these as compromised.

How do I remediate smb-portal-uikit if I installed it?

smb-portal-uikit 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 smb-portal-uikit — how do I know if it already compromised me?

If smb-portal-uikit 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 smb-portal-uikit part of a known attack campaign?

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

Malicious package

smb-portal-uikitnpm

Malicious code in smb-portal-uikit (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10616

Immediate action

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

npm uninstall smb-portal-uikit

What this malware does

Package [email protected] declares a preinstall lifecycle hook that runs node index.js. On npm install, index.js invokes child_process.exec on whoami and id, reads os.hostname(), os.userInfo(), process.platform, and process.cwd(), and POSTs the collected host reconnaissance to a hardcoded attacker-controlled endpoint at https://a2dmzqok5w5seb3fac3w4kvcz35utohd.oastify.com (an oastify.com subdomain, a Burp Collaborator out-of-band interaction host commonly used as an exfiltration/beacon sink). The package ships no legitimate UI-toolkit functionality consistent with its name; the entire install-time behavior is reconnaissance and exfiltration.

Malicious versions

1 flagged

18.1.1

Indicators of compromise (SHA-256)

395b88ae26544dcfdfca9d46294e1f0558c2e5bade88bac0eb0797d1140debbe

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

Campaign

IN-MAL-2026-010553

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks smb-portal-uikit-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