Which versions of bajkvahzv8allnltvr7x4s5hdxkjvyji are malicious?

Every published version of bajkvahzv8allnltvr7x4s5hdxkjvyji on npm is considered malicious. Remove the package entirely.

How do I remediate bajkvahzv8allnltvr7x4s5hdxkjvyji if I installed it?

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

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

Yes — bajkvahzv8allnltvr7x4s5hdxkjvyji is associated with the GHSA-rh8g-2jpx-ghwc 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 bajkvahzv8allnltvr7x4s5hdxkjvyji across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bajkvahzv8allnltvr7x4s5hdxkjvyji (all published versions).

Malicious package

bajkvahzv8allnltvr7x4s5hdxkjvyjinpm

Advisory published Jul 30, 2026Updated Jul 31, 2026

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

Malicious code in bajkvahzv8allnltvr7x4s5hdxkjvyji (npm)

MAL-2026-11244

Immediate action

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

npm uninstall bajkvahzv8allnltvr7x4s5hdxkjvyji

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

33a3ac75333df2fe3d27eac3d771269f45d3567ec6203fc00b8e9b9234897744

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bajkvahzv8allnltvr7x4s5hdxkjvyji (all published versions).
If you installed it — respond
Remove bajkvahzv8allnltvr7x4s5hdxkjvyji 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 bajkvahzv8allnltvr7x4s5hdxkjvyji 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. bajkvahzv8allnltvr7x4s5hdxkjvyji on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rh8g-2jpx-ghwc

References

github.com

Detect & block this

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