Which versions of @mosfe/owl-config are malicious?

The following npm versions of @mosfe/owl-config are flagged malicious: 1.0.8. Treat any of these as compromised.

How do I remediate @mosfe/owl-config if I installed it?

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

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

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

Search your lockfiles and build artifacts for @mosfe/owl-config (version 1.0.8).

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

Malicious package

@mosfe/owl-confignpm

Advisory published Jun 25, 2024Updated Oct 24, 2024

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

Malicious code in @mosfe/owl-config (npm)

MAL-2024-2817

Immediate action

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

npm uninstall @mosfe/owl-config

Malicious versions

1 flagged

1.0.8

Indicators of compromise (SHA-256)

05b07159ec026ef5c188dd881e0906348db54ab15b478c3e1e61549f5036aab9

2e8b3e4f2fdc5c139d951b5bc34beac14bf3691440f1a59c1910ac27e81f40a5

f89871eb25633d6ded72003bc755c646ea1fd24e999dddadbb5b73aeadadf15d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-00139RLUA-2024-05982

Credits

ReversingLabs · finder

Detect & block this

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