Which versions of style-to-objact are malicious?

The following npm versions of style-to-objact are flagged malicious: 99.9.0. Treat any of these as compromised.

How do I remediate style-to-objact if I installed it?

Remove style-to-objact 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 style-to-objact — how do I know if it already compromised me?

If style-to-objact 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 style-to-objact part of a known attack campaign?

Yes — style-to-objact is associated with the RLMA-2026-05325, RLUA-2026-06513 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 style-to-objact across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for style-to-objact (version 99.9.0).

Malicious package

style-to-objactnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

style-to-objact is a confirmed malicious npm package (MAL-2026-7425) that executes malicious code on install (malicious version 99.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in style-to-objact (npm)

MAL-2026-7425

Immediate action

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

npm uninstall style-to-objact

Malicious versions

1 flagged

99.9.0

Indicators of compromise (SHA-256)

53fe135e265ff524af980a87c06e5a66d88183e8069a8eceea68e26a16152206

31517073122d060e8675cfc8c93c99c68080234e50764ff452db247c6c07c936

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05325RLUA-2026-06513

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks style-to-objact-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