bjs-lint-builder
This report shows the evidence for bjs-lint-builder@1.0.5, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-2880 confirms this npm version as malicious.
Advisory
MAL-2026-2880
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in bjs-lint-builder (npm)
Details
big.js typosquat campaign - SSH backdoor implantation, credential and crypto wallet theft
---
## Source: amazon-inspector (de4578f36842f930e2a5e6a4129c10eb87bf1005fe8cbdf05ffb9fdc2fe43ad8) The package bjs-lint-builder was found to contain malicious code.
## Source: ghsa-malware (c24cf196d54bfa6bb62a2c9f5a1d6c4bef51af8986282f5a3a81688c46a2b7f8) 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to bjs-lint-builder@1.0.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing bjs-lint-builder@1.0.5. 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: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.