Our slopsquatting detector had three ways to say "safe". None of them needed evidence.
说明与用途
Slopsquatting 检测器原先依赖签名构建、早期注册和缺失创建日期的规则,现已更新:移除不可靠规则,记录所有低风险决策及其日期和来源,风险评估基于包的年龄和注册日期。
问题
Language models suggest package names that may not exist, enabling attackers to register those names (slopsquatting) and trick developers into installing malicious code.
结果
The updated detector no longer relies on weak evidence, records low-risk decisions for audit, and improves reliability against slopsquatting attacks.
工作流
- Collect suggested package names from language models.
- Query registries (npm, PyPI, Go modules) for each name.
- Apply age-based risk ladder: <14 days high, <60 days medium, otherwise low.
- Remove rule that accepted signed build statements as low risk.
- Remove rule that accepted early registration as low risk.
- Replace missing creation date rule with Go module date from deps.dev.
- Record every low verdict with rule, registration date, and first sighting date.
- Re-score previously withdrawn findings under new rules.
- Plan to audit rule 2 by plotting registration dates against collection start date once data accumulates.
证据
Ask a language model which package to use and, now and then, it names one that does not exist.
A package that appeared last week and matches a name models keep inventing deserves suspicion.
If it has a signed build statement, return low risk.
If it was registered before anyone suggested it, return low risk.
If info.created_at is None, return low risk.
Now every low verdict is recorded with the rule that produced it, the registration date and our first sighting.
- 记录日期: 2026-10-02T04:40:42.049Z