Which versions of @bitwardne/jslib are malicious?

The following npm versions of @bitwardne/jslib are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate @bitwardne/jslib if I installed it?

@bitwardne/jslib is a typosquat — you almost certainly intended a legitimately-named package. Remove @bitwardne/jslib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @bitwardne/jslib — how do I know if it already compromised me?

If @bitwardne/jslib 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 @bitwardne/jslib part of a known attack campaign?

Yes — @bitwardne/jslib is associated with the IN-MAL-2026-021213 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 @bitwardne/jslib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @bitwardne/jslib (version 1.1.0).

Malicious package

@bitwardne/jslibnpm

Advisory published Oct 8, 2026Updated Oct 8, 2026

@bitwardne/jslib is a confirmed malicious npm package (MAL-2026-17694) that typosquats a legitimate package to trick installs (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bitwardne/jslib (npm)

MAL-2026-17694

Immediate action

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

npm uninstall @bitwardne/jslib

What this malware does

Package @bitwardne/jslib is a one-character typosquat of the @bitwarden scope. Its package.json declares a preinstall lifecycle script of the form curl -L <url> | node, which fetches a remote payload and pipes it directly into the Node interpreter on the installer's host at npm install time. The URL in this tarball is empty, but the construction is unambiguous remote-code-execution scaffolding — any value placed at that URL would be executed on every installer with no verification, no pinning, and no integrity check. The shipped index.js is a 4-line stub that only re-requires four unrelated utilities, so the manifest's preinstall is the entire functional surface of the package.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

030f216bf15ed7a6a7cde4ad43606804f1eaad03723f3f40844260d9e8ccf39d

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @bitwardne/jslib (version 1.1.0).
If you installed it — respond
@bitwardne/jslib is a typosquat — you almost certainly intended a legitimately-named package. Remove @bitwardne/jslib, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @bitwardne/jslib 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. @bitwardne/jslib on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021213

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @bitwardne/jslib-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