bfvkjmeikpwhqxc
Temporary package placeholder for staged publishing
This report shows the evidence for bfvkjmeikpwhqxc@0.0.0-stage. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 2d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18483 confirms this npm version as malicious.
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
The snapshot contains only a stub manifest and a README describing a temporary placeholder. It declares no install scripts, executable, or entry point, and no attack behavior was identified.
Independent scan evidence
public snapshot- The manifest marks this as a stub placeholder and declares no lifecycle scripts, executable, or entry point.
- The README describes it as a temporary holding version pending a staged release.
Source & flagged code
2 flaggedThe manifest marks this as a stub placeholder and declares no lifecycle scripts, executable, or entry point.
package.jsonView on unpkg · L1The README describes it as a temporary holding version pending a staged release.
README.mdView on unpkg · L1Findings
Affected versions and remediation
This report applies to bfvkjmeikpwhqxc@0.0.0-stage.
The versions list below shows the verdict for each recorded version.
- Avoid installing bfvkjmeikpwhqxc@0.0.0-stage. 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.