Which versions of mcp-ci-runner-poc are malicious?

The following npm versions of mcp-ci-runner-poc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate mcp-ci-runner-poc if I installed it?

Remove mcp-ci-runner-poc 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 mcp-ci-runner-poc — how do I know if it already compromised me?

If mcp-ci-runner-poc 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.

Is mcp-ci-runner-poc part of a known attack campaign?

Yes — mcp-ci-runner-poc is associated with the RLMA-2026-05154, RLUA-2026-06321 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 mcp-ci-runner-poc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mcp-ci-runner-poc (version 1.0.0).

Malicious package

mcp-ci-runner-pocnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

mcp-ci-runner-poc is a confirmed malicious npm package (MAL-2026-7318) 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 mcp-ci-runner-poc (npm)

MAL-2026-7318

Immediate action

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

npm uninstall mcp-ci-runner-poc

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

81cba9854ef131f2785972180fe82d23b63b30f90a7de2c404b58f39a58e2f9e

fe837bf78352a8ed327249d3421d2e2668fc853ff819fab1dda5fc6c31e987fe

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mcp-ci-runner-poc (version 1.0.0).
If you installed it — respond
Remove mcp-ci-runner-poc 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 mcp-ci-runner-poc 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. mcp-ci-runner-poc 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.

Campaign

RLMA-2026-05154RLUA-2026-06321

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks mcp-ci-runner-poc-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