Which versions of scriptstierium11 are malicious?

The following npm versions of scriptstierium11 are flagged malicious: 20.26.51, 22.26.51. Treat any of these as compromised.

How do I remediate scriptstierium11 if I installed it?

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

If scriptstierium11 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is scriptstierium11 part of a known attack campaign?

Yes — scriptstierium11 is associated with the GHSA-xmg5-m82w-23mq, RLMA-2025-04018, RLUA-2026-01548 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 scriptstierium11 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for scriptstierium11 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scriptstierium11 across your stack and pipelines.

Malicious package

scriptstierium11npm

scriptstierium11 is a confirmed malicious npm package (MAL-2025-5727) that executes malicious code on install (malicious versions 20.26.51, 22.26.51). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in scriptstierium11 (npm)

MAL-2025-5727

Immediate action

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

npm uninstall scriptstierium11

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

20.26.5122.26.51

Indicators of compromise (SHA-256)

1e266c41818b3bf14da762f866026f1e266e51c7991db31ff0b165c66cd7ba04

68bcda2c9230ecf518fb64dccafd2be5d73de22a3c87e5e51c13db340060c354

de8d76e60ac4a2fa89e6a27cde15049750f93f7bea768938ba5384aa3ed28506

4568c0c4d8d75744d6494819d93be8d45f7a8bc313013a32d27802fa3ddb4760

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for scriptstierium11 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scriptstierium11 across your stack and pipelines.
If you installed it — respond
Remove scriptstierium11 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 scriptstierium11 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks scriptstierium11 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. scriptstierium11 on npm has been identified as a malicious package (versions 20.26.51, 22.26.51 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xmg5-m82w-23mqRLMA-2025-04018RLUA-2026-01548

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks scriptstierium11-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