Which versions of @self-sell/self-sell-amplitude-events are malicious?

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

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

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

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

Yes — @self-sell/self-sell-amplitude-events is associated with the GHSA-wpwp-fhhx-377c, RLMA-2025-04879, RLUA-2026-01055 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/self-sell-amplitude-events 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/self-sell-amplitude-events (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/self-sell-amplitude-events across your stack and pipelines.

Malicious package

@self-sell/self-sell-amplitude-eventsnpm

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

MAL-2025-47046

Immediate action

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

npm uninstall @self-sell/self-sell-amplitude-events

What this malware does

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

ae064f7137baf9c1292997ecd4204537d8011af89721c3d0878247049cd7a20f

c9009004db390c63cbecc127c16176a295e32f81b7be55e0566b91ba90f264b3

dea4f01421e418eb75b46322e66afb58ca79b89bc34f0d0f3eb40622da17d7f0

553bbfcd56694b7a2c7f6837ebd645bd77df9606c034d59b687baaef87157621

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/self-sell-amplitude-events (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/self-sell-amplitude-events across your stack and pipelines.
If you installed it — respond
Remove @self-sell/self-sell-amplitude-events 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/self-sell-amplitude-events 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/self-sell-amplitude-events 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/self-sell-amplitude-events 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-wpwp-fhhx-377cRLMA-2025-04879RLUA-2026-01055

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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