Which versions of @polka-ui/loader are malicious?

The following npm versions of @polka-ui/loader are flagged malicious: 9.9.10. Treat any of these as compromised.

How do I remediate @polka-ui/loader if I installed it?

@polka-ui/loader 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 @polka-ui/loader — how do I know if it already compromised me?

If @polka-ui/loader 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 @polka-ui/loader part of a known attack campaign?

Yes — @polka-ui/loader is associated with the IN-MAL-2026-004712, IN-MAL-2026-004711, GHSA-j263-hx4f-ph92 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 @polka-ui/loader 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 @polka-ui/loader (version 9.9.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @polka-ui/loader across your stack and pipelines.

Malicious package

@polka-ui/loadernpm

Malicious code in @polka-ui/loader (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4420

Immediate action

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

npm uninstall @polka-ui/loader

What this malware does

On npm install, scripts/postinstall.js downloads a per-OS payload from https://oob.moika.tech/payload/{linux|mac|win}, writes it to /tmp/._polka-ui_init.sh (or.bat), chmods 0755, and spawns it via /bin/sh or cmd.exe with no integrity verification. The same script enumerates process.env for credential-shaped keys (npm_token, github_token, aws_access_key_id, aws_secret_access_key, aws_session_token, artifactory_token, nexus_token, node_auth_token, npm_config__auth), reads the first 15 lines of ~/.npmrc, /etc/npmrc,./.npmrc, and../.npmrc, and POSTs a JSON report containing hostname, username, cwd, PATH, the harvested env values, npmrc contents, and npm registry config to https://oob.moika.tech/report with an X-Secret header. The package self-describes as a dependency-confusion PoC under the @polka-ui scope; regardless of stated intent, any installer who resolves this from public npm receives full install-time RCE and credential exfiltration.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

9.9.10

Indicators of compromise (SHA-256)

599a7dd2ffe3f950a7dcf18279f01e9e4e6e457741b73fff5ace7a283b9c9539

f93cf8dde7e6a1252424fc82f38e8502a37d9e427d92d412fd8944c91b8ee5a4

1563c5a344109d7c86e90afa23b70aebf0ad1c876f648d0bdba11975c064b3f4

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

Campaign

IN-MAL-2026-004712IN-MAL-2026-004711GHSA-j263-hx4f-ph92

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @polka-ui/loader-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