Which versions of @mosfe/lion are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for @mosfe/lion (version 0.0.3).

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

Malicious package

@mosfe/lionnpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

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

Malicious code in @mosfe/lion (npm)

MAL-2024-2622

Immediate action

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

npm uninstall @mosfe/lion

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

b4f0f73cde90fa700cd05ca704e2de498263f8250cc975bf48cb5c147b52c9c8

36b80b9c43878b9fcc8aed305662313481e89b04be8f14377a4f8cb33984d2b1

cc8d50679dbc4e69e1db2ccd710ec2be0fe4ae3a7f617b95c88d1e5f882e32f7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-00138RLUA-2024-05981

Credits

ReversingLabs · finder

Detect & block this

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