Which versions of byvendors are malicious?

The following npm versions of byvendors are flagged malicious: 99.0.5, 99.0.6. Treat any of these as compromised.

How do I remediate byvendors if I installed it?

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

If byvendors 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.

How do I find byvendors across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for byvendors (2 malicious versions).

Malicious package

byvendorsnpm

Advisory published May 11, 2026Updated May 12, 2026

byvendors is a confirmed malicious npm package (MAL-2026-3423) that executes malicious code on install (malicious versions 99.0.5, 99.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in byvendors (npm)

MAL-2026-3423

Immediate action

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

npm uninstall byvendors

What this malware does

The package byvendors was found to contain malicious code.

The OpenSSF Package Analysis project identified 'byvendors' @ 99.0.6 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

99.0.599.0.6

Indicators of compromise (SHA-256)

1b7d770b773df64355a4fac410adc86f9778e470efdcc18ede73eb6024a3f982

ab8502681753baebb6a3e3746e3a7d591f7557b4f15a1865b536f78c38db991f

3d3ae01e4f5473c61cf7c26fdf51f64fa34c7f16451ce6c093a52fd85b79eff5

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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