OCInferno
open-sourceThe section your link pointed to isn't on OCInferno's page any more, so we've brought you to the top.
OCInferno is an OCI offensive-security framework for credential handling, service enumeration, artifact download, configuration auditing, and graph-based attack-path analysis.
run exploit_kubernetes_clusters_rpst --cluster-id ocid1.cluster.oc1.phx.. run exploit_datascience_pipelines_rpst --project-id ocid1.datascienceproject.oc1.. --log-group-id ocid1.loggroup.oc1.. --cleanup ocinferno enum_identity --save-domains ocinferno enum_all --regions us-ashburn-1,us-phoenix-1 ocinferno exploit_remove_authentication_factors
Summary
OCInferno is an open-source, BSD-3-Clause-licensed exploitation framework for Oracle Cloud Infrastructure, run as a Python command-line tool installed from PyPI. Modeled on Pacu, it handles credential and workspace management, service enumeration, artifact download, and configuration auditing, with modules that extract resource-principal tokens from OKE clusters and Data Science pipelines and exploit modules for stripping MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. or working against DevOps repositories; a dedicated module exports OpenGraphOpenGraphA web metadata protocol, created by Facebook, that lets a webpage declare structured properties—title, image, description, type—so link previews render consistently across social platforms and messaging apps. JSON that feeds into BloodHound for privilege-escalation path mapping. It's aimed at cloud penetration testers and red teamers working OCI engagements rather than at defenders, and the README describes it as the OCI sibling of GCPwn, its sister project for Google Cloud. With two contributors but 73 commits and four releases in the past year, the most recent just 16 days old, it is under active, if small-team, development.
OCInferno is an OCI offensive-security framework for credential handling, service enumeration, artifact download, configuration auditing, and graph-based attack-path analysis.
How OCInferno helps
Which identities in this tenancy have a path to a more privileged role than they should?
generates OpenGraph output from enumerated identity, resource, and policy data and feeds it into BloodHound, drawing the privilege-escalation edges between principals and resources so a path can be traced hop by hop
What credentials can I pull out of a compromised OKE node or Data Science pipeline run?
runs dedicated exploit modules that extract the resource principal token from instance metadata or injected pipeline steps, then converts it into a usable bearer token without needing the OCI CLI or workload-identity federation
Which regions or services did an enumeration run fail to reach?
scopes a run to chosen regions and marks any module that hits a connect or read timeout, so stalled or unsupported endpoints are visible instead of silently missing from the results
What does this tenancy's configuration expose that shouldn't be public?
runs a set of configuration checks across enumerated services and records the findings to a queryable local store for review after the run
Can I strip a target account's MFA once I have initial access?
includes an exploit module that removes classic and identity-domain MFA factors from an OCI account, with the pre-collected credentials from the workspace supplying the access needed
What's actually sitting in this tenancy's DevOps repositories?
enumerates DevOps repository resources and downloads their contents, prompting before any git operation so the action taken against the target is visible before it runs
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for OCInferno, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail OCInferno puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
2 entries
No entries match these filters.
- September 20261
- August 20261
Project health
Issue, contributor and maintainer activity in NetSPI/OCInferno, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 +1 vs prior 12 months
- Maintainers 1 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close not measured first maintainer reply 27 days
- Open backlog 1 of 1 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 0
- Commits / month 0
- Stars 22
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →