Which versions of @b2bgeo/yav are malicious?

The following npm versions of @b2bgeo/yav are flagged malicious: 13.3.7, 13.3.8. Treat any of these as compromised.

How do I remediate @b2bgeo/yav if I installed it?

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

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

Yes — @b2bgeo/yav is associated with the RLMA-2024-00025, RLUA-2024-05876 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 @b2bgeo/yav 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 @b2bgeo/yav (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @b2bgeo/yav across your stack and pipelines.

Part of a larger attack: @b2bgeo published 15 malicious packages. See the full campaign →

Malicious package

@b2bgeo/yavnpm

@b2bgeo/yav is a confirmed malicious npm package (MAL-2024-3978) that executes malicious code on install (malicious versions 13.3.7, 13.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @b2bgeo/yav (npm)

MAL-2024-3978

Immediate action

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

npm uninstall @b2bgeo/yav

Malicious versions

2 flagged

13.3.713.3.8

Indicators of compromise (SHA-256)

2ab46691744706ed94c915ffe5c826eb437eab8a1fda69011b9e853750d7b971

3a56d98abc18c7744f7fe3da647d7e058518baea7a986cb64f25a6b93a0cb4e5

73e7793529d7c1edf197812ccc8e68c75806f30139b22777b84e61a8631c3e11

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

Campaign

RLMA-2024-00025RLUA-2024-05876

References

security.snyk.io

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @b2bgeo/yav-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