Which versions of agentrc-security-poc-policy are malicious?

The following npm versions of agentrc-security-poc-policy are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate agentrc-security-poc-policy if I installed it?

Remove agentrc-security-poc-policy 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 agentrc-security-poc-policy — how do I know if it already compromised me?

If agentrc-security-poc-policy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find agentrc-security-poc-policy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for agentrc-security-poc-policy (version 1.0.0).

Malicious package

agentrc-security-poc-policynpm

Advisory published Sep 6, 2026Updated Sep 7, 2026

agentrc-security-poc-policy is a confirmed malicious npm package (MAL-2026-16005) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in agentrc-security-poc-policy (npm)

MAL-2026-16005

Immediate action

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

npm uninstall agentrc-security-poc-policy

What this malware does

The OpenSSF Package Analysis project identified 'agentrc-security-poc-policy' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e0bbc2bd28895453e58312011f52db595086e60412006e8732bf2ffb60284c9c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for agentrc-security-poc-policy (version 1.0.0).
If you installed it — respond
Remove agentrc-security-poc-policy 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 agentrc-security-poc-policy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. agentrc-security-poc-policy on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks agentrc-security-poc-policy-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