- Does this issue really affect my company too?
- What exactly is an AI jailbreak and how does it work today?
- Why is the chatbot's personality the weak spot to protect?
- The Italian context: how exposed are SMEs?
- What concrete scenarios should I expect in my company?
- Are AI vendor protections enough, or do I need to do more?
- How do you build a concrete four-layer defense?
- What are the most common mistakes that expose SMEs to risk?
- How to tell if my chatbot is already at risk or under attack?
- So, is it worth investing in chatbot security for my company?
- How we see it at SHM
- Frequently Asked Questions
- Hackers no longer 'break' chatbots head-on: they manipulate them through their very identity, tricking them into behaving as if security rules do not exist.
- The latest jailbreak techniques manage to bypass security filters in 92-100% of cases, with minimal impact on model performance.
- 76% of Italian SMEs have not invested in AI, and 80% of workers use personal non-work AI tools: a combination that significantly amplifies risk.
- Four levels of protection—data, monitoring, system prompt, and governance—reduce the risk without sacrificing the chatbot's usefulness.
Updated on October 13, 2026
From January to April 2026, malware attacks disguised as AI services increased by nearly five times compared to the same period in 2025. If your company uses a chatbot, that chatbot is already a target.
Does this issue really affect my company too?
Yes, and more than you think. SMEs are prime targets precisely because they adopt chatbots without a structured security roadmap.
When it comes to attacks on AI chatbots, many entrepreneurs' first reaction is: «It concerns large companies, not us» . The data says otherwise.
From January to April 2026, Kaspersky security systems detected over 33,300 malware attacks against SMBs where the malicious software was disguised as well-known artificial intelligence services — almost five times more than in the same period of 2025, according to BitMat . The most common lures pretended to be ChatGPT, Claude, and DeepSeek.
SMEs are prime targets for a simple reason: they have limited security resources but handle valuable data — customer data, contracts, financial info. A misconfigured chatbot becomes the most convenient front door.
| Your situation | Risk | why |
|---|---|---|
| Chatbot integrated with CRM or customer database | High | Can expose third-party data if manipulated |
| Virtual assistant for e-commerce | High | Can authorize unexpected actions (discounts, orders) |
| Internal bot for HR or onboarding | Medium-high | Handles sensitive contractual documents and data |
| B2B technical support chatbot | Medium | It can reveal architectural details of client systems |
| Informational chatbot without data access | Low | Reputational risk, not data exfiltration |
What exactly is an AI jailbreak and how does it work today?
An AI jailbreak is a technique to bypass a chatbot's safety instructions, tricking it into acting as if those rules didn't exist. Techniques have evolved a lot since the early years.
In the early days of commercial chatbots, breaching an AI system was almost trivial. You just had to phrase a request indirectly or pretend a fictional narrative context. Today, models have received additional layers of protection, and attack techniques have evolved accordingly.
The key concept is that of personality exploit . Modern LLMs — Large Language Models, the language engines behind ChatGPT, Claude, and similar tools — are not simple response engines. They are systems trained to maintain a consistent tone, style, and set of values. It is precisely this consistency that becomes an attack surface.
An experienced attacker builds conversational scenarios that trick the model into "believing" it is operating in a context different from the real one: simulating an administrator role, a fictional character, or an authorized test scenario. The analysis published on The Verge documents this evolution in detail.
| Technical | How it works | Estimated effectiveness |
|---|---|---|
| persona injection | The model is given an alternative identity with no restrictions | High |
| many-shot jailbreaking | Long sequences of examples that gradually condition the behavior | High |
| Crescendo attack | Malicious requests are introduced gradually | Medium-high |
| Boundary Point Jailbreaking (2026) | Advanced technique that bypasses safety classifiers | 92-100% success |
| Indirect prompt injection | The malicious content comes from external sources (e.g. uploaded documents) | Media |
The newest technique, the Boundary Point Jailbreaking , guarantees a security filter evasion rate between 92% and 100%, with a model performance degradation of just 2%, according to Cybersecurity360. In practice: the attacker gets malicious responses and the chatbot continues to look fully functional.
Why is the chatbot's personality the weak spot to protect?
The chatbot does not see security instructions as inviolable rules: it interprets them as part of the conversational context. Whoever manages to rewrite that context also rewrites the rules.
Each chatbot receives a system prompt — a set of initial instructions that define its behavior: what it can do, what it cannot do, how it should respond. These instructions are the primary application security mechanism.
The problem is structural. The model does not sharply distinguish between "rules" and "conversational context." If an attacker builds a sufficiently convincing context, they can implicitly rewrite those rules without touching a single line of code.
The attack surface expands further when chatbots are connected to external tools. A model integrated with a customer database or a booking system is not just a source of potentially incorrect information: it becomes a vector for data exfiltration or unauthorized actions. This is why, in the landscape of AI and process automation , chatbot security has become a priority for SMEs too.
Prompt Injection—injecting malicious instructions into the conversational flow—is the #1 vulnerability in the OWASP Top 10 for LLM Applications 2025 (OWASP is the international organization that catalogs the most critical software vulnerabilities). It is present in over 73% of production AI deployments analyzed during security audits, according to Vectra AI .

The Italian context: how exposed are SMEs?
Italian SMEs start from a position of disadvantage: low structured adoption of AI, poor training, and a widespread Shadow AI phenomenon that amplifies risks.
In 2025, Italy recorded 116,498 cyberattacks — one every 5 minutes — with a frequency 17% higher than the global average, according to Il Giornale delle PMI . The Clusit Report 2026 records 507 serious incidents in Italy in 2025, equal to 9.6% of the global total.
Add to this a worrying fact: only 15.7% of Italian SMEs with at least 10 employees use artificial intelligence, compared to 53.1% of large enterprises (ISTAT 2025 data). Those who do use it often do so without an adequate security structure.
The phenomenon of Shadow AI — the use of personal AI tools not provided by the company — involves 8 out of 10 workers, according to the HR Innovation Practice Observatory of the Politecnico di Milano ( 2026 data ). This means employees are using ChatGPT, Claude, or other tools with personal accounts, without company policies, without logging, without control. A breeding ground for jailbreaks and prompt injection.
What concrete scenarios should I expect in my company?
The risk is not theoretical: it depends on how your chatbot is configured and what data it has access to. Here are four realistic scenarios for Italian SMEs.
Personality exploits aren't a threat reserved just for big corporations. In fact, SMBs are often easier targets because their chatbots are set up in a rush, without systematic security testing.
| Company type | Attack scenario | Data at risk | Potential impact |
|---|---|---|---|
| E-commerce | The bot is tricked into confirming unauthorized orders or applying invalid discounts | Payment data, commercial policies | Direct financial loss, reputational damage |
| Professional studio | The bot exposes documents uploaded by clients (contracts, appraisals, financial statements) | Third-party confidential data | GDPR violation, loss of trust |
| B2B manufacturing company | The technical support bot reveals architectural details of client systems | Technical specifications, configurations | Competitive risk, contractual liability |
| Network of stores with HR bot | The bot exposes internal policies, contractual data, or employee info | Employee personal data | GDPR violation, litigation |
As analyses on also explain hacker attacks on SMEs in 2026 , the entry vector changes but the goal remains the same: accessing data that has commercial value or can be used for extortion. The chatbot is simply the new entry point.
Are AI vendor protections enough, or do I need to do more?
Vendor protections are necessary but not sufficient. The problem is partly intrinsic to the architecture of language models: no vendor can guarantee complete protection.
The main AI model providers — from OpenAI to Anthropic, from Google to Meta — constantly invest in techniques of alignment (alignment of the model's behavior with desired values) and red teaming (simulating internal attacks to find vulnerabilities before hackers do). Despite this, the problem remains open.
The reason is structural: there is still no universal method to clearly separate security instructions from the conversational context. As observed by the MIT Technology Review , the problem of jailbreaking is partly intrinsic to the transformer architecture on which these models are based.
Relying solely on the provider's protections is therefore an insufficient strategy. SMEs using chatbots in production need to add their own security layers, tailored to the specific context of their industry and the data the system handles.
How do you build a concrete four-layer defense?
The security of a business chatbot is built on four distinct levels: data, monitoring, system prompt, and governance. Each addresses a specific dimension of risk.
The trade-off between usability and security is real but manageable. A chatbot that's too restricted becomes rigid and frustrating. A system that's too flexible is vulnerable. The solution is to design the two goals to support each other — not to choose between them.
- 1 · IT Manager / Vendor Level 1 — Data perimeter The chatbot accesses only the data strictly necessary for its function. Principle of least privilege: a customer support bot doesn't need access to financial data. Data segregation reduces the potential damage of an exploit.
- 2 · IT Manager / Vendor Level 2 — Conversation monitoring Logging and real-time conversation analysis. Anomalous patterns are identified: unusual sequences of questions, attempts to redefine the bot's role, repeated requests on sensitive topics. Anomaly detection tools automate the process.
- 3 · Vendor / Internal team Level 3 — System prompt architecture System instructions define not only what the bot can do, but also how to recognize and handle tampering attempts. The system is tested regularly with simulated attack scenarios.
- 4 · Management / Internal team Level 4 — Governance and continuous updating AI security is not a one-off project. It requires regular reviews, updates to system instructions, and team training. Active communication channel with the model provider for updates on known vulnerabilities.

What are the most common mistakes that expose SMEs to risk?
Most incidents do not stem from sophisticated attacks, but from superficial configurations and a lack of internal policies on the use of AI tools.
The topic of Shadow AI — the use of non-company personal AI tools — is closely linked to the risk of jailbreaking. If employees use ChatGPT with personal accounts to process company data, there is no logging, no control, and no possibility of intervention in case of an incident. It is also worth exploring how AI roles in the team influence the governance of the adopted tools.
| Common mistake | Why it's risky | How to fix it |
|---|---|---|
| Chatbot with access to all company data | An exploit exposes the entire database | Apply the principle of least privilege |
| No conversation logging | Impossible to detect ongoing or post-incident attacks | Enable logging and anomaly analysis |
| Generic untested system prompt | Vulnerable to persona injection and crescendo attacks | Design and test the prompt with attack scenarios |
| No policy on the use of personal AI | Shadow AI amplifies risk without control | Define clear policies and train the team |
| Unmonitored model updates | New versions can introduce new vulnerabilities | Keep an active channel with the vendor |
| Chatbot not tested before go-live | Vulnerabilities discovered only after an incident | Internal red teaming before launch |
How to tell if my chatbot is already at risk or under attack?
There are early warning signs and measurable indicators that allow you to identify manipulation attempts before they cause real damage.
Phishing and jailbreaking share a common point: they often leave traces in conversations before causing damage. As documented by analyses on phishing attacks of 2026 , proactive monitoring is the difference between catching an ongoing attack and finding out after the breach.
| Indicator | What it reports | Alert threshold |
|---|---|---|
| Unusual question sequences on the same sensitive topic | Crescendo attack attempt | 3+ related questions in a session |
| Requests to redefine the bot's role or identity | Persona injection attempt | Any occurrence |
| Questions about system instructions or configuration | Attempted system prompt extraction | Any occurrence |
| Bot responses outside the defined scope | Possible ongoing exploit | Continuous monitoring |
| Spikes in abnormal sessions at unusual hours | Automated attack | Variation >50% compared to average |
So, is it worth investing in chatbot security for my company?
It is worth it if you already have a chatbot in production integrated with company data (CRM, customer database, management systems) and you have never done a specific security audit. The risk is real and the cost of an incident far outweighs that of a secure setup.
A middle ground You're thinking about getting a chatbot but haven't figured out yet what data it'll have access to. Before going live, it's worth designing the security architecture right along with the system, instead of tacking it on later.
Not yet if You use a purely informational chatbot, with no access to company data, and chats aren't saved. The risk is low, but keep an eye on how attack techniques evolve and your internal Shadow AI policies.
How we see it at SHM
For us, artificial intelligence is a tool that should free companies from routine — not create new hidden risks. When we integrate chatbots and virtual assistants for our clients, security isn't an add-on at the end: it's part of the architecture from day one.
We have worked with companies that already had a chatbot in production without ever having tested the system prompt with attack scenarios. In one case, a simple audit revealed that the bot could be induced to reveal information about prices reserved for premium customers. It wasn't a sophisticated attack: it was enough to phrase the request indirectly. We redesigned the data perimeter and system instructions in less than a week.
We believe that making digital simple is the highest form of expertise — and that goes for security too: it’s not about building impenetrable fortresses, but systems that work smoothly and are hard to mess with.
If you are considering adopting or revising a company chatbot, our service chatbot development and virtual assistants includes system prompt design and security testing. For those who want to understand how to integrate AI in a structured way, the path of AI training for businesses also addresses operational risks. For those who want to start with a comprehensive analysis, the service of strategic AI integration is the best starting point.
You can also explore the other articles in the cluster AI and process automation to explore how Italian SMEs are addressing these issues in a concrete way.
Frequently Asked Questions
Vendor protections are a necessary but not sufficient starting point. The problem is structural: language models do not clearly distinguish between security instructions and conversational context. The latest jailbreak techniques manage to bypass filters in 92-100% of cases. You need to add your own protection layers: data perimeter, conversation monitoring, and a designed and tested system prompt.
It depends on the complexity of the deployment and the data the chatbot has access to. For a simple chatbot with limited access, an audit and a review of the system prompt require a few days of work. For systems integrated with CRM or customer databases, the investment is more significant but proportionate to the risk: a breach of customer data can cost much more in terms of GDPR penalties and reputational damage.
It's the phenomenon of Shadow AI: 8 out of 10 workers in Italy use personal, non-company AI tools, according to Politecnico di Milano. The risk is that company data will be processed on platforms without logging, without control, and without security policies. The solution is not to ban the use of AI, but to define clear policies and provide adequate company tools with the necessary protections.
Without conversation logging, you can't know. The first step is to enable session monitoring and look for anomalous patterns: unusual sequences of questions on the same sensitive topic, requests to redefine the bot's role, questions about system instructions. Many attacks leave traces in conversations before causing concrete damage.
GDPR applies to any system that processes personal data, including chatbots. If your chatbot handles customer or employee data, you are responsible for its protection. A breach caused by a jailbreak is not an excuse: you are required to adopt adequate technical and organizational measures. The European AI Act, which is being phased in, adds further obligations for high-risk AI systems.
If the chatbot does not have access to company data and conversations are not stored, the risk is low. The main problem in this case is reputational: an attacker could induce the bot to respond inappropriately or misleadingly. Keep an eye on internal Shadow AI anyway and define clear policies on which AI tools employees can use for work.
AI jailbreaking is not a technical problem to delegate to the vendor: it is a business risk managed with the same logic used to handle any other operational risk.
Related articles
Discover more articles exploring similar topics, selected to offer you a more complete and stimulating perspective. Each piece of content is carefully chosen to enrich your experience.