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

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

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

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

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

Yes — @self-sell/components is associated with the GHSA-4rr2-7m4q-j5gh, RLMA-2025-04877, RLUA-2026-01053 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/components 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/components (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/components across your stack and pipelines.

Malicious package

@self-sell/componentsnpm

@self-sell/components is a confirmed malicious npm package (MAL-2025-47044) that executes malicious code on install (malicious version 1.2.9213). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @self-sell/components (npm)

MAL-2025-47044

Immediate action

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

npm uninstall @self-sell/components

What this malware does

The package @self-sell/components 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)

aeb15f4ae1c1a830e2fdc21bd8a903fe2e14978eb9952f1e5b3f98f0ca7f353f

4107da12a5fd4148213157fad524ccf86bf0169516c34547bc68d275a213f157

91f9ee3e10cc0e526ac3fc9b6705e25ceb2473d36a30629bbf0a2b94facdc984

750ebc3321f4eaaf1dffd69e9da54dd24d5d24e59740c0c412343a7eb77eb595

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/components (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/components across your stack and pipelines.
If you installed it — respond
Remove @self-sell/components 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/components 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/components 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/components 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-4rr2-7m4q-j5ghRLMA-2025-04877RLUA-2026-01053

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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