Which versions of @gameforge/http-server are malicious?

The following npm versions of @gameforge/http-server are flagged malicious: 99.9.99. Treat any of these as compromised.

How do I remediate @gameforge/http-server if I installed it?

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

If @gameforge/http-server 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 @gameforge/http-server part of a known attack campaign?

Yes — @gameforge/http-server is associated with the RLMA-2026-01855 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 @gameforge/http-server across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @gameforge/http-server (version 99.9.99).

Malicious package

@gameforge/http-servernpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

@gameforge/http-server is a confirmed malicious npm package (MAL-2026-2714) that executes malicious code on install (malicious version 99.9.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @gameforge/http-server (npm)

MAL-2026-2714

Immediate action

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

npm uninstall @gameforge/http-server

What this malware does

The package @gameforge/http-server was found to contain malicious code.

Malicious versions

1 flagged

99.9.99

Indicators of compromise (SHA-256)

c0fd7ce78f539e21d7d738533b81cfeb21b839e3cd76f2eb3827f828366e4a79

c5c80f200c1cbaa194dfc83e5a8c911c182ff110b7451512013646d9414429b4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01855

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @gameforge/http-server-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