Which versions of @mosfe/beam are malicious?

The following npm versions of @mosfe/beam are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate @mosfe/beam if I installed it?

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

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

Yes — @mosfe/beam is associated with the RLMA-2024-00134, RLUA-2024-05977 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 @mosfe/beam across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mosfe/beam (version 2.0.0).

Part of a larger attack: @mosfe published 10 malicious packages. See the full campaign →

Malicious package

@mosfe/beamnpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

@mosfe/beam is a confirmed malicious npm package (MAL-2024-1816) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mosfe/beam (npm)

MAL-2024-1816

Immediate action

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

npm uninstall @mosfe/beam

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

c8904a5c441310d67dec28ff5e4727bbe6b48574e9bb260da90142f0797f31de

202fbf1e8cdde5a0ff889322d595e1eb65238d6841809564d242674eb083d3f8

558e826228263002fcac71432dc78027d6c582028774d12bc98fec5414cf4df8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-00134RLUA-2024-05977

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @mosfe/beam-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