IQ.Lvbs alleges unauthorized access attempts from Comma.ai IP address
Startup claims rival’s IP targeted its sign-in system and driving model during a private beta phase in October.
Key points
- IQ.Lvbs reported repeated attempts to steal its NovaSpark model and exploit its sign-in system.
- The alleged requests originated from an IP address assigned to Comma.ai Inc.
- IQ.Lvbs team members were banned from Comma.ai’s Discord channel shortly after the incident began.
IQ.Lvbs alleges that its IT infrastructure faced unauthorized access attempts targeting its NovaSpark driving model and user authentication systems. The startup claims these activities originated from an IP address linked to rival Comma.ai, according to a blog post.
Root cause
IQ.Lvbs stated that the incident occurred while promoting NovaSpark, the first model for its IQ.Pilot app, which requires Comma.ai camera hardware. The startup introduced the private beta in Comma.ai’s Discord channel on October 3. According to the company, the subsequent unauthorized requests aimed to steal the model and access private driving files.
Attack path
From October 7 to October 14, IQ.Lvbs reported repeated attempts to exploit its sign-in system and access user devices. The blog post claims the first requests came from an IP assigned to Comma.ai Inc. On October 8, IQ.Lvbs team members were banned from the Comma.ai Discord channel, followed by bans for private beta testers.
Affected versions
- NovaSpark private beta model
- IQ.Pilot application sign-in system
- IQ.Lvbs internal IT systems
Mitigation
- Verify IP addresses of incoming requests to authentication endpoints.
- Audit Discord channel permissions and ban logs for unauthorized changes.
- Review access controls for private beta distribution channels.
- Monitor for unusual attempts to access proprietary model files.
Detection notes
Security teams should monitor authentication logs for repeated failed sign-in attempts or requests from unexpected IP ranges. Check for unusual access patterns to sensitive repositories or model files. Review application logs for spikes in traffic from specific sources. Ensure that beta testing platforms have strict access controls and that only authorized users can interact with proprietary assets.
What to do and how to stay safe: IQ.Lvbs
- Monitor authentication logs for repeated failed login attempts from unusual IP addresses.
- Audit access permissions for beta testing platforms and proprietary software repositories.
- Verify the source of incoming requests to critical infrastructure components.
- Once the vendor provides an update, apply patches to authentication systems immediately.
Step-by-step guide: Phishing Defenses: Answers to 10 Critical Questions
General security guidance from the BlueTeam Insider newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
Did Comma.ai confirm the hack attempt?
No, Comma.ai did not confirm the allegations; the claims originate solely from IQ.Lvbs.
What was the target of the alleged attack?
The target was IQ.Lvbs’ NovaSpark model, user devices, and sign-in system.
When did the alleged attacks occur?
The alleged attacks occurred from October 7 to October 14.
