Which versions of plugin-proposal are malicious?

The following npm versions of plugin-proposal are flagged malicious: 99.1.1. Treat any of these as compromised.

How do I remediate plugin-proposal if I installed it?

Remove plugin-proposal 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 plugin-proposal — how do I know if it already compromised me?

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

Yes — plugin-proposal is associated with the RLMA-2026-05225, RLUA-2026-06381 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 plugin-proposal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for plugin-proposal (version 99.1.1).

Malicious package

plugin-proposalnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

plugin-proposal is a confirmed malicious npm package (MAL-2026-7348) that executes malicious code on install (malicious version 99.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in plugin-proposal (npm)

MAL-2026-7348

Immediate action

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

npm uninstall plugin-proposal

Malicious versions

1 flagged

99.1.1

Indicators of compromise (SHA-256)

331df7af0be6439644cf2b516311d11277915ee9dd1948d85e59f1c739cc8d1c

def92e257441f58e0e76cdf67b90e40d312097f9ebf246ed490c743eafce74e3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for plugin-proposal (version 99.1.1).
If you installed it — respond
Remove plugin-proposal 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 plugin-proposal 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. plugin-proposal on npm has been identified as a malicious package (version 99.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05225RLUA-2026-06381

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks plugin-proposal-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