Which versions of @maximvs1538/os-npm are malicious?

The following npm versions of @maximvs1538/os-npm are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @maximvs1538/os-npm if I installed it?

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

If @maximvs1538/os-npm 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 @maximvs1538/os-npm part of a known attack campaign?

Yes — @maximvs1538/os-npm is associated with the RLMA-2026-04756, RLUA-2026-05886 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 @maximvs1538/os-npm across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @maximvs1538/os-npm (version 99.0.0).

Malicious package

@maximvs1538/os-npmnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@maximvs1538/os-npm is a confirmed malicious npm package (MAL-2026-7084) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @maximvs1538/os-npm (npm)

MAL-2026-7084

Immediate action

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

npm uninstall @maximvs1538/os-npm

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

b41a95adfb0fe895da026e59895dfef70bbb56233d892a90808d81b753ddeef0

1122084e69378e31b23005d31fbc5258ab9ff5ca0e8dc311b4541c65d372e7fe

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04756RLUA-2026-05886

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @maximvs1538/os-npm-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