Cropwise (Syngenta Group) was listed on 02 June 2026 by the ShadowByt3$ ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). ShadowByt3$ listed 3 organizations that month and 25 in total.
- Listed 171 days ago.
- 708 organizations were listed by all groups in June 2026, see the month.
- 39 in Agriculture and Food Production that month.
- 5 in CH that month.
Updated 2026-11-19 05:43 UTC. Data: public leak-site listings. How we work.
Cropwise (Syngenta Group)
Threat Group Post & Evidence
- Listed by
- ShadowByt3$ 25 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
We have breached you and gained access to the following portals: https://operations.cropwise.com/d/users/sign_in https://accounts.cropwise.com/signin proof: https://mega.nz/folder/25hkSLgY#ELjJaFie-TfES9Z_47KFZA company url: https://operations.cropwise.com/ We are ShadowByt3$ a Extortion as a service group. You have been breached and 10.4MB was stolen. It may seem small but it can affect you every way imaginable. Don't believe us the following below was stolen: 👤 User Identities and Access Credentials - Account Directory Data: Full names, corporate email addresses, and phone numbers of registered agronomists, regional farm managers, and field staff. - Authentication Metadata: Encrypted password hashes, session tokens, or configured API keys utilized to link automated machinery data feeds to the web dashboard. 🚜 Precision Agronomy and Farm Metrics - Geospatial Boundaries: High-resolution …
Show the full post (2216 characters)
We have breached you and gained access to the following portals: https://operations.cropwise.com/d/users/sign_in https://accounts.cropwise.com/signin proof: https://mega.nz/folder/25hkSLgY#ELjJaFie-TfES9Z_47KFZA company url: https://operations.cropwise.com/ We are ShadowByt3$ a Extortion as a service group. You have been breached and 10.4MB was stolen. It may seem small but it can affect you every way imaginable. Don't believe us the following below was stolen: 👤 User Identities and Access Credentials - Account Directory Data: Full names, corporate email addresses, and phone numbers of registered agronomists, regional farm managers, and field staff. - Authentication Metadata: Encrypted password hashes, session tokens, or configured API keys utilized to link automated machinery data feeds to the web dashboard. 🚜 Precision Agronomy and Farm Metrics - Geospatial Boundaries: High-resolution GIS boundary files detailing the exact shapes, coordinates, and property lines of privately owned or leased commercial fields. - Vegetation and Scouting Analyses: Historical NDVI satellite imagery datasets [CWO: Tools for effective monitoring of your crops' condition syngenta.co.za], past growth tracking matrices, field problem zone flags, and yield prediction models. - Operational Treatment Records: Deep operational histories documenting exact pesticide or fertilizer applications, crop types, seeding timelines, and harvesting schedules. 🚛 Telematics and Fleet Diagnostics - Machinery Tracking Logs: Real-time and archived GPS location paths generated by connected tractors, combines, or sprayers. These logs map out the specific work shifts, operational speeds, and field locations of individual machine drivers. If you contact us then we won't leak it and show proof that we deleted it. Also we will tell you how to secure your company so you don't get breached again. We are giving you 48 hours (approx 3 days) to contact us which would be by June 4th 2026. If you fail to reach out to us we will maximize damage by giving it to news outlets, swatting victims, and we will email everyone affected and you would be the next headline. All you have to do is pay 1 million in bitcoin or monero and it goes away.
Amounts as written
- 10.4MB
Kinds of data mentioned
-
Passwords and credentials
“…believe us the following below was stolen: 👤 User Identities and Access Credentials - Account Directory Data: Full names, corporate email addresses, and phone numbers of registered…”
-
Email and communications
“…and Access Credentials - Account Directory Data: Full names, corporate email addresses, and phone numbers of registered agronomists, regional farm managers, and field…”
-
Medical or patient records
“…types, seeding timelines, and harvesting schedules. 🚛 Telematics and Fleet Diagnostics - Machinery Tracking Logs: Real-time and archived GPS location paths generated by connected…”
-
Employee and HR records
“…phone numbers of registered agronomists, regional farm managers, and field staff. - Authentication Metadata: Encrypted password hashes, session tokens, or configured API keys…”
Plain-English summary AI-written
The group says it stole 10.4 MB of data, including user identities, access credentials, account directory data, and authentication metadata.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Cropwise (Syngenta Group) (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Cropwise (Syngenta Group) directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Cropwise (Syngenta Group) can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: email and communications, passwords and credentials, employee and hr records.
- If you share health data with them You may be the data controller, with notification duties of your own. Ask counsel which health-privacy rules apply to you. Why: The post names medical or health data.
Within 30 days
- Keep watching Cropwise (Syngenta Group) A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Cropwise (Syngenta Group)
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: passwords and credentials, email and communications.
Within 3 days
- Handle health-data exposure Work out which patient or health records are in scope, apply the health-privacy notification rules that cover them, and prepare patient communications. Why: The post names: medical or patient records.
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 10.4MB. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties Health data adds sector rules. This is general guidance, not legal advice: confirm current rules with counsel. Why: The listing or sector points to health data.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Agriculture and Food Production organizations and ask them whether they were affected. Why: ShadowByt3$ listed 1 other Agriculture and Food Production organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
56/100 • GUARDEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceNo scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.
Open the full attack surface scan →Run a free passive scan on your own domain to see what an attacker can see from the outside.