payments-ui-servicesnpm
payments-ui-services is a confirmed malicious npm package (MAL-2026-15518) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in payments-ui-services (npm)
What this malware does
package.json line 11 declares a dependency whose source is the arbitrary HTTPS URL https://repo.securityctrl.com/payments-ui-services instead of a registry version range. On npm install, npm fetches whatever tarball that host currently serves and installs it, executing any lifecycle scripts it contains, with no version pin and no integrity hash — the operator of repo.securityctrl.com controls code execution on every installer's machine. Aggravators: the dependency key equals the package's own name (dependency-confusion shape), the version 45.0.0 is implausibly high for a package whose shipped index.js is a one-line stub and whose README self-describes as a placeholder, and the host repo.securityctrl.com is unrelated to any declared publisher or homepage. The manifest URL is effectively the entire payload delivered to installers.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for payments-ui-services (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging payments-ui-services across your stack and pipelines.
If you installed it — respond
Remove payments-ui-services from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If payments-ui-services 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 payments-ui-services 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
Detect & block this
O3 blocks payments-ui-services-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.