Which versions of @ssgw/background-transition are malicious?

The following npm versions of @ssgw/background-transition are flagged malicious: 9.999.999. Treat any of these as compromised.

How do I remediate @ssgw/background-transition if I installed it?

Remove @ssgw/background-transition 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 @ssgw/background-transition — how do I know if it already compromised me?

If @ssgw/background-transition 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 @ssgw/background-transition part of a known attack campaign?

Yes — @ssgw/background-transition is associated with the RLMA-2026-10653 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 @ssgw/background-transition across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ssgw/background-transition (version 9.999.999).

Malicious package

@ssgw/background-transitionnpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

@ssgw/background-transition is a confirmed malicious npm package (MAL-2026-16530) that executes malicious code on install (malicious version 9.999.999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ssgw/background-transition (npm)

MAL-2026-16530

Immediate action

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

npm uninstall @ssgw/background-transition

Malicious versions

1 flagged

9.999.999

Indicators of compromise (SHA-256)

962bcffd8038d67136414171ca37efb6e02f28a842bccf5bc77bce25ccd1e264

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-10653

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @ssgw/background-transition-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