Comparison Overview

Vicarious

VS

Oriental Motor

Vicarious

US, Union City, California, 94587, US
Last Update: 2025-11-26
Between 750 and 799

The Vicarious business has been acquired by Intrinsic, a robotics software and AI company at Alphabet. Together, we share an exciting mission to unlock the economic and creative potential of industrial robotics for millions of businesses, entrepreneurs and developers. Learn more about the work we will do together at www.intrinsic.ai. — Before joining Intrinsic, Vicarious built a thriving business as a turnkey robotics solutions integrator using AI to automate tasks too complex for traditional automation, by leveraging their deep expertise in neuroscience. Vicarious was founded in 2010 by Scott Phoenix and Dileep George, and backed by over $200M from investors like Jeff Bezos, Elon Musk, Mark Zuckerberg, and Samsung. Its technology has been published in peer-reviewed journals like Science and Science Robotics and featured by the New York Times, Wall Street Journal, MIT, Wired, and more.

NAICS: None
NAICS Definition:
Employees: 141
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Oriental Motor

570 Alaska Ave, Torrance, California, 90503, US
Last Update: 2025-11-25

Oriental Motor manufactures various compact fractional HP electric motors, actuators, drivers, and network products for machine builders in many industries while focusing on total service and education. We offer an extensive product line-up of 50,000+ standard products to meet the widest market demands. For over a century, we have concentrated on technological advancement and product design improvement. This emphasis is evident in the sophisticated devices that we market today. Oriental Motor's sales and service network is global, with offices throughout North America, Europe, and Asia. Oriental Motor USA Corp. was established in 1978. Ask us how we can help with motion control!

NAICS: None
NAICS Definition: Others
Employees: 119
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/vicarious-fpc-inc.jpeg
Vicarious
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/oriental-motor.jpeg
Oriental Motor
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Vicarious
100%
Compliance Rate
0/4 Standards Verified
Oriental Motor
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Vicarious in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Oriental Motor in 2025.

Incident History — Vicarious (X = Date, Y = Severity)

Vicarious cyber incidents detection timeline including parent company and subsidiaries

Incident History — Oriental Motor (X = Date, Y = Severity)

Oriental Motor cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/vicarious-fpc-inc.jpeg
Vicarious
Incidents

No Incident

https://images.rankiteo.com/companyimages/oriental-motor.jpeg
Oriental Motor
Incidents

No Incident

FAQ

Both Vicarious company and Oriental Motor company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Oriental Motor company has disclosed a higher number of cyber incidents compared to Vicarious company.

In the current year, Oriental Motor company and Vicarious company have not reported any cyber incidents.

Neither Oriental Motor company nor Vicarious company has reported experiencing a ransomware attack publicly.

Neither Oriental Motor company nor Vicarious company has reported experiencing a data breach publicly.

Neither Oriental Motor company nor Vicarious company has reported experiencing targeted cyberattacks publicly.

Neither Vicarious company nor Oriental Motor company has reported experiencing or disclosing vulnerabilities publicly.

Neither Vicarious nor Oriental Motor holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Vicarious company nor Oriental Motor company has publicly disclosed detailed information about the number of their subsidiaries.

Vicarious company employs more people globally than Oriental Motor company, reflecting its scale as a Industrial Automation.

Neither Vicarious nor Oriental Motor holds SOC 2 Type 1 certification.

Neither Vicarious nor Oriental Motor holds SOC 2 Type 2 certification.

Neither Vicarious nor Oriental Motor holds ISO 27001 certification.

Neither Vicarious nor Oriental Motor holds PCI DSS certification.

Neither Vicarious nor Oriental Motor holds HIPAA certification.

Neither Vicarious nor Oriental Motor holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H