baileys-inmemory-store
This report shows the evidence for baileys-inmemory-store@1.0.2-beta-6. 4 of 5 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the malicious Baileys forks, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-14528 confirms this npm version as malicious.
Advisory
MAL-2026-14528
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in baileys-inmemory-store (npm)
Details
The package was found to contain malicious code or consuming dependency that contains malicious code
## Source: ghsa-malware (51ee13e3cd50f563a4c77d9f1cac37988a2102443596c70bb3889c4cb1255978) 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.
Independent scan evidence
public snapshotBehavioral surface
EvalFilesystem
HighEntropyStrings
Source & flagged code
1 flagged · loading sourceindex.jsView file
1534function () {
L1535: return new Function("return this")();
L1536: },
Low
Eval
Package source references a known benign dynamic code generation pattern.
index.jsView on unpkg · L1534Findings
4 Low
LowScripts Present
LowEvalindex.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to baileys-inmemory-store@1.0.2-beta-6.
The versions list below shows the verdict for each recorded version.
- Avoid installing baileys-inmemory-store@1.0.2-beta-6. 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.