Which versions of tabbables are malicious?

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

How do I remediate tabbables if I installed it?

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

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

Yes — tabbables is associated with the IN-MAL-2026-019081 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 tabbables 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 tabbables (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 tabbables across your stack and pipelines.

Malicious package

tabbablesnpm

tabbables is a confirmed malicious npm package (MAL-2026-15524) 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 tabbables (npm)

MAL-2026-15524

Immediate action

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

npm uninstall tabbables

What this malware does

package.json at line 11 declares a dependency whose key equals the package's own name (tabbables) and whose value is the raw HTTPS URL https://repo.securityctrl.com/tabbables rather than a registry version range. On npm install, npm fetches whatever tarball that URL currently serves and installs it, executing any lifecycle scripts it contains, with no version pin, no integrity/hash check, and no registry provenance. The shipped index.js is an inert stub, so the manifest URL is the sole payload-delivery mechanism; the tarball's behavior can be changed at any time by whoever controls repo.securityctrl.com. The self-referential dependency key also produces a dependency-confusion shape (an implausibly high 45.0.0 version competing with any internal package of the same name).

Malicious versions

1 flagged

45.0.0

Indicators of compromise (SHA-256)

2fc629ecaf81d15034bbba33363e63776d106e6f58932e889baa4cb748b689eb

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 tabbables (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 tabbables across your stack and pipelines.
If you installed it — respond
Remove tabbables 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 tabbables 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 tabbables 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. tabbables 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-019081

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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