[BUG]Baileys sometimes sends messages to incorrect remoteJid (random number that doesn’t exist)

[hassangeekshub]

I’m experiencing an intermittent issue with Baileys where my bot sometimes responds to the wrong conversation.

Expected behavior:
When a user sends a message, Baileys should respond to the same remoteJid from which the message was received.

Actual behavior:
Occasionally, Baileys interprets the remoteJid incorrectly.
Example:

Correct remoteJid from incoming message: 123456@s.whatsapp.net but instead received message from 654231@s.whatsapp.net and replying, Baileyssends to 654231@s.whatsapp.net, which is not even an existing WhatsApp number.

This causes the bot to create a new conversation with this random number instead of replying in the correct thread.

Frequency:
Happens sporadically, not every message, but enough to cause problems in production.

Environment:

Baileys version: 6.7.18

Node.js version: 22

Platform: Ubantu

you can see messages are send to a random number

[amanv08]

Can you share the code like where you are receiving the message and then sending it.

[hassangeekshub]

issue is first message from contact contain lid only and when we reply from our whatsapp after that new messages are start comming from Jid but there are 2 chats for same contact created on whatsapp

[rovannlinhalis]

Same problem with me — the received message appears with a strange contact. When sent through the platform, the message is not delivered to the correct contact and, on the phone, it shows up as a new contact from a number that doesn't exist

[tomiheneldra]

@hassangeekshub @rovannlinhalis Please include your code/function for handling and sending messages to make it clearer.

[hassangeekshub]

@hassangeekshub @rovannlinhalis Please include your code/function for handling and sending messages to make it clearer.

here is code
so when contact send first message sometimes i get 55xxxxxx@s.whatsapp.net which actual number and everything works
fine but
sometimes first message comes from 123xxxxx@lid instead of actual number and bot reply using this 123xx@lid and when contact reply back then i get 55xxxxxx@s.whatsapp.net (which is actual number) and bot reply to that when but on whatsapp 2 chats starts appearing for same contact

so i think there should be a function getJidFromLid

 async sendText(id: string, number: string, message: string)
 {
    const sock = this.manager.getSession(id);
    if (!sock) throw new NotFoundException(`No active session for ${id}`);
    await sock.sendMessage( number, { text: message });
  }

[bobslavtriev]

your code === problem
true

[LucasVinicius314]

here's an example payload that causes this issue:

{
  "key": {
    "remoteJid": "785781145265907@lid",
    "fromMe": false,
    "id": "3AE3DAA02001087D93E0"
  },
  "messageTimestamp": 1754595942,
  "pushName": "Name",
  "broadcast": false,
  "message": {
    "conversation": "Hello?",
    "messageContextInfo": {
      "deviceListMetadata": {
        "senderTimestamp": "1754590359",
        "recipientKeyHash": "...",
        "recipientTimestamp": "1753705535"
      },
      "deviceListMetadataVersion": 2,
      "messageSecret": "..."
    }
  },
  "messageType": "conversation"
}

just like hassangeekshub said, it happens once in a while, but that's enough to cause problems in production

as you can see, the remote jid is a linked device id, and not a @s.whatsapp.net jid. and because of this, there's no way of knowing who sent you the message since the id is just an id and not a real number

I haven't tested the baileys nightly version in production yet because I'm not sure what other issues it could cause, but this is a real issue that's been haunting me for a few weeks and I haven't found a solution yet, maybe it has something to do with coexistence from what I read in similar issues

[FilipePaiva10]

Realmente isso é complicado, a única maneira que fiz para resolver isso foi investigando.. para esses que tem o lid@ na versão nova vem o senderPn Daí eu uso para pegar o número.. mas só envio a mensagem conforme o remotejId.. Ao final do dia pego e identifico os duplicados e unifico para resolver.. sempre levando o número e o lid do contato para comparar e não duplicar mais..

[raseldev18]

your code === problem
true

ini terus jawabannya, minimal kasi solusi

[tomiheneldra]

your code === problem
true

ini terus jawabannya, minimal kasi solusi

please check the following issue because it has been resolved before #1564

[gandalfhv]

tu código === problema
verdadero

ini terus jawabannya, mínimo kasi solusi

Por favor, revise el siguiente problema porque ya se resolvió antes del n.° 1564.

NO es cierto, el problema se esta extendiendo, con la version Nightly Release se puede obtener SenderPn que trae el numero real del remitente, pero si el bot envia un mensaje a ese numero, el remitente solo obtiene "Esperando el mensaje. Esto puede tomar tiempo."

[matheusprogff]

Did you manage to solve it? I'm always having the problem when the bot's greeting is triggered, it ends up responding to the real contact and triggering the greeting to random numbers.

[jorgejuniordev]

`# NPM
npm install @whiskeysockets/baileys@WhiskeySockets/Baileys#add-lid-to-message-key

YARN v2

yarn add @whiskeysockets/baileys@WhiskeySockets/Baileys#add-lid-to-message-key`

[adrielCarmo]

same problem here... any solution?