isMalicious
1.2.0 commercialThe section your link pointed to isn't on isMalicious's page any more, so we've brought you to the top.
Product updates, API improvements, and release notes for the isMalicious threat intelligence platform.
curl https://ismalicious.com/cve/CVE-2024-1234
curl -X POST https://ismalicious.com/api-docs/bulk \
-H 'Authorization: Bearer <token>' \
-H 'Content-Type: application/json' \
-d '{"indicators": ["203.0.113.42", "evil-domain.example", "http://phish.example/login"]}'
curl -u '<api-key>:' \
https://ismalicious.com/taxii/collections/ \
-H 'Accept: application/taxii+json;version=2.1'
curl -X POST https://ismalicious.com/api-docs/bulk \
-H 'Authorization: Bearer <api_key>' \
-H 'Content-Type: application/json' \
-d '{
"indicators": [
{"type": "ip", "value": "192.168.1.1"},
{"type": "domain", "value": "evil.com"},
{"type": "url", "value": "http://malicious.org/phish"}
]
}'
curl -X GET https://ismalicious.com/api/dns/history --header 'Authorization: Bearer <API_KEY>' -d '{"domain": "example.com", "records": ["A", "MX"]}'
GET /methodology
Summary
isMalicious is a commercial threat intelligence tool that checks IP addresses, domains, URLs, file hashes, and certificates against records of malicious activity, run as a hosted API rather than installed software. Its endpoints cover bulk checking, case management for tracking investigations, and a TAXIITAXIIA protocol for sharing threat intelligence over HTTPS, commonly carrying STIX data. It lets tools retrieve and exchange intelligence from compatible services. interface for pulling and sharing indicator collections in standard formats, alongside stats on CVE exploitation likelihood (EPSSEPSSExploit Prediction Scoring System, an estimate of the probability that a published vulnerability will be exploited in the next 30 days. It helps prioritize investigation and patching.) over time, which points it at SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts and threat-intel teams building detection or enrichment pipelines rather than at individual researchers doing one-off lookups. This breadth of endpoints — reputation, WHOIS, geolocation, vulnerability data, each queryable separately — puts it in the category of consolidated lookup services people otherwise assemble from several single-purpose feeds. The project is actively maintained, with 17 releases in the tracked window and the most recent one 30 days ago.
Product updates, API improvements, and release notes for the isMalicious threat intelligence platform.
How isMalicious helps
Is this IP, domain, or URL associated with known malicious activity?
runs the indicator against the reputation, WHOIS, certificate, geolocation, and vulnerability data behind the core check and returns a verdict for each dimension rather than one combined score
Which of a large batch of indicators need attention right now?
accepts many IPs, domains, or URLs in a single submission and returns per-indicator results, so a list can be triaged without one lookup per entry
Is a domain's certificate or WHOIS history consistent with a legitimate site?
separates certificate data and WHOIS data into their own calls, so registration age or a mismatched certificate can be checked independently of the reputation verdict
Where geographically does traffic to or from a flagged address originate?
returns geolocation for an indicator as its own call, tying the address to a location without bundling it into the general reputation answer
Is a suspicious indicator worth opening a formal investigation over?
lets a case be opened directly from a lookup, with evidence attached and tracked over time alongside alert trends and a risk-brief feed
Are the alerts trending up or down across the indicators this team watches?
the alert-trends feed reports pattern changes over time, separate from any single indicator check, so a rise in activity is visible before a specific lookup would surface it
Languages
Command line
3 commands for isMalicious, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
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
Five scores for isMalicious, 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 isMalicious 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
32 entries
No entries match these filters.
- November 20261
- October 20266
- September 20267
- August 20262
- April 20266
- March 20265
- February 20263
- January 20262
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 →