Which versions of oci-plugin-compliance are malicious?

The following npm versions of oci-plugin-compliance are flagged malicious: 1.9.9. Treat any of these as compromised.

How do I remediate oci-plugin-compliance if I installed it?

Remove oci-plugin-compliance 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.

I already installed oci-plugin-compliance — how do I know if it already compromised me?

If oci-plugin-compliance 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 oci-plugin-compliance part of a known attack campaign?

Yes — oci-plugin-compliance is associated with the GHSA-67r4-3x8x-9vgx, RLMA-2025-05099, RLUA-2026-01470 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 oci-plugin-compliance 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 oci-plugin-compliance (version 1.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oci-plugin-compliance across your stack and pipelines.

Malicious package

oci-plugin-compliancenpm

oci-plugin-compliance is a confirmed malicious npm package (MAL-2025-47334) that executes malicious code on install (malicious version 1.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oci-plugin-compliance (npm)

MAL-2025-47334

Immediate action

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

npm uninstall oci-plugin-compliance

What this malware does

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

1.9.9

Indicators of compromise (SHA-256)

762cb43037a71931178ccf3452552b84331b30ada3f192f5d979eed5b372da3f

a06afa5fc985fdc9802d29dcbbffbf44061db17206f41a976cc8656c94d63e40

7ac0ffd1c9b953c431f565ab7fc52bcf284dd186ebef946f06a37291e466b646

39ea79c5b2428e1bd704a9da4f23e38e22f349fd92093169cbcf189f2473ed7c

7971a562a5ebb052563db5b6f149bdf1dd86e45b94f31dd0715bdd9c2cedf66b

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for oci-plugin-compliance (version 1.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oci-plugin-compliance across your stack and pipelines.
If you installed it — respond
Remove oci-plugin-compliance 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 oci-plugin-compliance 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 oci-plugin-compliance 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. oci-plugin-compliance on npm has been identified as a malicious package (version 1.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-67r4-3x8x-9vgxRLMA-2025-05099RLUA-2026-01470

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks oci-plugin-compliance-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