@rivianlabs/dt-lib-lumberjack
Security research placeholder published as part of authorized Rivian Bug Bounty disclosure (Intigriti report RIVIAN-79L374RT). Triager Aurelius explicitly invited this claim. Intended for transfer to Rivian Inc. Contact: pahpah@intigriti.me
This report shows the evidence for @rivianlabs/dt-lib-lumberjack@0.0.1, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-3350 confirms this npm version as malicious.
Advisory
MAL-2026-3350
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @rivianlabs/dt-lib-lumberjack (npm)
Details
The package @rivianlabs/dt-lib-lumberjack was found to contain malicious code.
## Source: ossf-package-analysis (2def6fb7e02da8f9736d66d11b7456b416dd69cdbd25a8c15d12746371f00bb7) The OpenSSF Package Analysis project identified '@rivianlabs/dt-lib-lumberjack' @ 0.0.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
References
Independent scan evidence
public snapshotBehavioral surface
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node ./beacon.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
1 High1 Low
HighInstall Time Lifecycle Scriptspackage.json
LowScripts Present
Affected versions and remediation
This report applies to @rivianlabs/dt-lib-lumberjack@0.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @rivianlabs/dt-lib-lumberjack@0.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.