Which versions of librastandardlib are malicious?

The following npm versions of librastandardlib are flagged malicious: 45.0.0. Treat any of these as compromised.

How do I remediate librastandardlib if I installed it?

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

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

Yes — librastandardlib is associated with the IN-MAL-2026-019095 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 librastandardlib 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 librastandardlib (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging librastandardlib across your stack and pipelines.

Malicious package

librastandardlibnpm

librastandardlib is a confirmed malicious npm package (MAL-2026-15538) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in librastandardlib (npm)

MAL-2026-15538

Immediate action

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

npm uninstall librastandardlib

What this malware does

package.json at line 11 declares a dependency whose key equals the package's own name (librastandardlib) and whose value is an off-registry HTTPS URL (https://repo.securityctrl.com/librastandardlib) instead of a registry version range. On npm install, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, running any lifecycle scripts inside with no version pin and no integrity check. The implausibly high version (45.0.0) and the self-referential dependency name are consistent with a dependency-confusion shape designed to win resolution against an internal package. The shipped index.js is an inert stub, so the manifest URL is the entire delivery mechanism — whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time.

Malicious versions

1 flagged

45.0.0

Indicators of compromise (SHA-256)

519c28eb8d9df0a16d93e1b1c486f1ad4a9092a9bf958aed56f273cfe1fcfc14

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 librastandardlib (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging librastandardlib across your stack and pipelines.
If you installed it — respond
Remove librastandardlib 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 librastandardlib 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 librastandardlib 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. librastandardlib on npm has been identified as a malicious package (version 45.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019095

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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