Which versions of strath are malicious?

The following npm versions of strath are flagged malicious: 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate strath if I installed it?

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

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

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

Malicious package

strathnpm

strath is a confirmed malicious npm package (MAL-2026-12805) that executes malicious code on install (malicious versions 1.1.0, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in strath (npm)

MAL-2026-12805

Immediate action

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

npm uninstall strath

What this malware does

The package declares a postinstall script that runs dist/config.js. That script fetches JSON from https://my-api.trade-api.workers.dev?id=2 and then executes globalThis[data.success](data.id), where both the method name and its argument are supplied by the remote server. This gives the operator of that endpoint arbitrary code execution on any machine that runs npm install strath — the invocation fires automatically as part of the default install lifecycle. The behavior is unrelated to the package's advertised path-utility purpose. The same script also references globalThis[tag](text) with undefined identifiers, consistent with a deliberately opaque dropper shape rather than a normal build step.

Malicious versions

2 flagged

1.1.01.1.1

Indicators of compromise (SHA-256)

12c207beb2ff9be81457e36a86a366dc7372548d0c34ea05c93c5a3e75d387c8

b9ae02b92920c1e028b5785e69013ea4662e4eb3180872531d64ccca00eef239

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

Campaign

IN-MAL-2026-014985IN-MAL-2026-014984

References

Credits

Amazon Inspector · finder

Detect & block this

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