Which versions of @alphasedboy/game are malicious?

The following npm versions of @alphasedboy/game are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate @alphasedboy/game if I installed it?

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

If @alphasedboy/game 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 @alphasedboy/game part of a known attack campaign?

Yes — @alphasedboy/game is associated with the RLMA-2026-04659, RLUA-2026-05804 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 @alphasedboy/game across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @alphasedboy/game (3 malicious versions).

Malicious package

@alphasedboy/gamenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@alphasedboy/game is a confirmed malicious npm package (MAL-2026-7034) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @alphasedboy/game (npm)

MAL-2026-7034

Immediate action

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

npm uninstall @alphasedboy/game

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

eecc0930279a792a303a67912b7644949cd7648b7ba5f2f41fdc83bf67ecd54a

90599ca44e984bc48a2ac904bfa4bc46c9272f9a481f5e789d178df049d97310

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @alphasedboy/game (3 malicious versions).
If you installed it — respond
Remove @alphasedboy/game 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 @alphasedboy/game 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. @alphasedboy/game on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04659RLUA-2026-05804

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @alphasedboy/game-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