Which versions of @self-sell/guards are malicious?

The following npm versions of @self-sell/guards are flagged malicious: 1.2.9213. Treat any of these as compromised.

How do I remediate @self-sell/guards if I installed it?

Remove @self-sell/guards 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 @self-sell/guards — how do I know if it already compromised me?

If @self-sell/guards 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 @self-sell/guards part of a known attack campaign?

Yes — @self-sell/guards is associated with the GHSA-74wh-pfj9-hm4q, RLMA-2025-04878, RLUA-2026-01054 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 @self-sell/guards 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 @self-sell/guards (version 1.2.9213). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @self-sell/guards across your stack and pipelines.

Malicious package

@self-sell/guardsnpm

Malicious code in @self-sell/guards (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-47045

Immediate action

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

npm uninstall @self-sell/guards

What this malware does

The package @self-sell/guards was found to contain malicious code.

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.2.9213

Indicators of compromise (SHA-256)

594bf67cf504a8b4b9f076c7913f69f5a9b3f0677a7528de143d2b247cf3bff7

3866c12b08c020ed846dec71cc0e2844bd7d69e83d0613662b84f15de248f7e5

1507ec8681356e3273090d182784ff2fbec290a1eab4b05d9785ca80de019b2e

b78429e1f2c86a744ce47be6ac8d0cb2ae456e6b71be51684168a874ebe85cb8

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 @self-sell/guards (version 1.2.9213). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @self-sell/guards across your stack and pipelines.
If you installed it — respond
Remove @self-sell/guards 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 @self-sell/guards 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 @self-sell/guards 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. @self-sell/guards on npm has been identified as a malicious package (version 1.2.9213 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-74wh-pfj9-hm4qRLMA-2025-04878RLUA-2026-01054

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @self-sell/guards-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