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

oit-lib-oracle-utilnpm

oit-lib-oracle-util is a confirmed malicious npm package (MAL-2026-15541) 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 oit-lib-oracle-util (npm)

MAL-2026-15541
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall oit-lib-oracle-util

What this malware does

package.json declares a dependency whose key (oit-lib-oracle-util) matches this package's own name and whose value is a bare HTTPS URL — https://repo.securityctrl.com/oit-lib-oracle-util — instead of a registry version range. On npm install, npm fetches whatever bytes that URL returns at install time and installs them, running any lifecycle scripts inside the fetched artifact. The source is unpinned, has no integrity hash, and is unrelated to the npm registry; the host repo.securityctrl.com is not a known registry mirror and has no association with a declared publisher. The shipped index.js is an inert stub, so the manifest itself is the entire delivery mechanism. The self-referential name and implausibly high version (45.0.0) are consistent with a dependency-confusion lure designed to win resolution against an internal package of the same name.

Malicious versions

1 flagged
45.0.0

Indicators of compromise (SHA-256)

63a2d32099a0c4246e0b8711f8b29d321b7d1c3a0a99e36edc367934fc9f34f3

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 oit-lib-oracle-util (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 oit-lib-oracle-util across your stack and pipelines.

  2. If you installed it — respond

    Remove oit-lib-oracle-util 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 oit-lib-oracle-util 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 oit-lib-oracle-util 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. oit-lib-oracle-util 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-019090

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks oit-lib-oracle-util-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
oit-lib-oracle-util (npm) malicious package — MAL-2026-15541 | O3 Security