Which versions of @rivianlabs/bedrock are malicious?

The following npm versions of @rivianlabs/bedrock are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate @rivianlabs/bedrock if I installed it?

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

If @rivianlabs/bedrock 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 @rivianlabs/bedrock across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @rivianlabs/bedrock (version 0.0.2).

Malicious package

@rivianlabs/bedrocknpm

Advisory published May 5, 2026Updated May 12, 2026

@rivianlabs/bedrock is a confirmed malicious npm package (MAL-2026-3348) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @rivianlabs/bedrock (npm)

MAL-2026-3348

Immediate action

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

npm uninstall @rivianlabs/bedrock

What this malware does

The package @rivianlabs/bedrock was found to contain malicious code.

The OpenSSF Package Analysis project identified '@rivianlabs/bedrock' @ 0.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

be028dadb5642a37a73b040b641fb6070be0adf328c27437477f4c5ddb64ec7a

7d12061e491ebc9109496b77ffd62384bba9a781ac9f0579343a61c5742df351

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @rivianlabs/bedrock (version 0.0.2).
If you installed it — respond
Remove @rivianlabs/bedrock 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 @rivianlabs/bedrock 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. @rivianlabs/bedrock on npm has been identified as a malicious package (version 0.0.2 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 @rivianlabs/bedrock-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