registry / rubbydev-crash-baileys / 0.0.0-stage
rubbydev-crash-baileys@0.0.0-stage
Temporary package placeholder for staged publishing
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.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package contains only a stub manifest and a placeholder README, with no executable source or lifecycle hooks. No concrete attack behavior was identified.
Static reason
No blocking static signals were detected.
Trigger
No install-time or runtime trigger is declared.
Impact
No harmful effect was identified from the inspected package source.
Mechanism
The package manifest contains only identity, stub status, and description fields.
AI rationale
The package contains only a stub manifest and a placeholder README, with no executable source or lifecycle hooks. No concrete attack behavior was identified.
Evidence
package.json
Decision evidence
public snapshotAI called this Clean at 99.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json marks the package as a stub and declares no lifecycle scripts or entrypoints.
Evidence against
Behavioral surface
NoLicense
Source & flagged code
1 flagged · loading sourcepackage.jsonView file
1{
"name": "rubbydev-crash-baileys",
"version": "0.0.0-stage",
"stub": true,
"description": "Temporary package placeholder for staged publishing"
}
Low
Suspicious Lifecycle Evidence
package.json marks the package as a stub and declares no lifecycle scripts or entrypoints.
package.jsonView on unpkg · L1Findings
2 Low
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to rubbydev-crash-baileys@0.0.0-stage.
See all versions of rubbydev-crash-baileys for other recorded verdicts.
- Review the evidence and your use of rubbydev-crash-baileys@0.0.0-stage before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.