Names carry freight in the Bible in a way ours mostly don’t. Nobody named a child Ichabod because they liked the sound of it.
And this stretch of 2 Samuel is a case study in what happens when a name gets quietly edited by later hands who couldn’t leave a bad memory alone — plus a detail about who actually did the killing in a royal assassination, which most of us skate right past on our way to the next chapter, and which turns out to be the sharpest thing in the whole passage.
The name that isn’t his name
Saul’s surviving son, propped up as a rival king by Abner, comes to us in English as Ish-bosheth. Man of shame. Which is a peculiar thing for a father to name a boy, and it turns out his father almost certainly didn’t.
Go looking for the same man in 1 Chronicles and you find him under another name entirely: Eshbaal (1 Chr 8:33; 9:39). Man of Baal — or, more carefully, since baʿal is also just an ordinary Hebrew noun for “lord” or “master” and not only the name of the Canaanite storm-god, something closer to the Lord exists. Then check Jonathan’s son: Merib-baal in Chronicles (8:34), Mephibosheth in Samuel. Same swap. Same family. Twice.
Here’s what happened. In the earliest stretch of Israel’s history, baʿal was an unremarkable element in a name — it meant “lord,” the way a family today might name a child something meaning the Lord is my strength without a second thought. But as Israel’s entanglement with actual Baal-worship deepened, and as the more polemical strands of the tradition took shape, later scribes went back through the records and swapped the baʿal element out for bosheth — shame — so the name could never again read as an accidental tip of the hat to the wrong god. It’s a pattern, not a one-off; scholars sometimes call it a scribal dysphemism, a deliberate downgrade baked permanently into the text.
Which is worth pausing on, because the obvious read is wrong. This wasn’t an insult his mother hung on him in the delivery room. It’s stranger than that, and colder. For centuries after the man was dust, the people copying and re-copying Israel’s scriptures could not bring themselves to leave his name alone. Every generation of scribes reached the page, saw the syllable, and changed it again. That’s not an insult. An insult is delivered once and forgotten. This is a verdict maintained on purpose, by hand, forever, inside the letters of a man’s own name.
A kingdom built out of body parts
Whatever we call him, his death is one of the ugliest scenes in this stretch, and the Hebrew is doing more work than a fast reading catches.
“Now the sons of Rimmon the Beerothite, Rechab and Baanah, set out, and about the heat of the day they came to the house of Ish-bosheth as he was taking his noonday rest… And they came into the midst of the house as if to get wheat, and they stabbed him in the stomach… When they came into the house, as he lay on his bed in his bedroom, they struck him and put him to death and beheaded him. They took his head and went by the way of the Arabah all night.” — 2 Samuel 4:5–7 (ESV)
Two of his own officers. Men who owed him their commissions. In his own house, at his own siesta, on the pretext of picking up grain — and then a night’s walk down the Jordan valley with a king’s head in a bag, to collect a bounty that turns out not to exist. David has them executed, exactly as he executed the man who showed up with Saul’s crown a few chapters earlier.
Now notice the body parts, because once you see the pattern you can’t unsee it.
Four verses before the murder, in the middle of an entirely different aside, the narrator stops to tell us Jonathan had a five-year-old son who was dropped by his nurse in the panic after Gilboa and “became lame” in both feet (4:4) — that’s Mephibosheth, carrying the same bosheth swap we just talked about, whose ruined feet will matter enormously several chapters later in a much kinder story. Then Ish-bosheth himself: when word of Abner’s murder reaches him, the Hebrew says his hands went slack (4:1) — the ESV smooths it to “his courage failed,” but the idiom is hands. Weak hands, and then a severed head. And at the end of the chapter, the assassins:
“And David commanded his young men, and they killed them and cut off their hands and feet and hanged them beside the pool at Hebron.” — 2 Samuel 4:12 (ESV)
The hands that did it. The feet that ran. Cut off and hung up at the town well where everybody comes for water.
Slack hands. Broken feet. A head in a bag. Hands and feet again, severed in judgment. Across a few dozen verses the narrator keeps building the meaning of this story out of the human body in pieces, and it isn’t decoration. It’s what a contested throne does to everyone standing near it. The kingmakers, the puppet, and finally the kingmakers again — all of them ending up in fragments, one way or another, courtesy of the ambition that put them in the room.
The detail almost everybody skips: who these two actually were
This is the part that gets the least attention and lands the hardest.
The narrator is fussy — genuinely fussy — about telling us where these men came from, and then he adds a parenthesis nobody asked for:
“…sons of Rimmon a man of Benjamin from Beeroth (for Beeroth also is counted part of Benjamin; the Beerothites fled to Gittaim and have been sojourners there to this day).” — 2 Samuel 4:2–3 (ESV)
Read that aside slowly, because it’s doing two things at once. Yes, Beeroth sits inside Benjamin’s territory — Saul’s own tribe. But Beeroth was one of the four Gibeonite towns (Josh 9:17): Canaanite cities that talked their way into a treaty with Israel back in Joshua’s day and were absorbed into the land without ever becoming Israelites. Territory, not bloodline. And the narrator goes out of his way to add that the Beerothites fled, and are living somewhere else as resident aliens to this day.
Fled from what? He doesn’t say here. But a long way further on, when a famine sits over the land for three years, David asks and gets an answer: “There is bloodguilt on Saul and on his house, because he put the Gibeonites to death” (2 Sam 21:1). The next verse spells it out — the Gibeonites weren’t Israelites, Israel had sworn an oath to spare them, and Saul had tried to wipe them out anyway in a fit of nationalist zeal.
The text never connects those dots out loud, and I want to be honest that the connection is an inference rather than a statement. But it is a short walk. Two men out of a Gibeonite town, whose people had been driven from their homes and were still displaced generations later, walk into the bedroom of Saul’s last son and kill him in his sleep.
Which means the ending of this story is not quite the one most of us tell. It isn’t simply his own countrymen turned on him — that reading needs Beeroth to be Benjaminite by blood, and it probably wasn’t. It’s older and much worse than that. Saul’s house went after a people it had sworn to protect, and a generation later the survivors of that people finished Saul’s house. The bloodguilt Saul incurred by the sword came back for his son on a bed at noon.
And nobody in the chapter says a word about it. David executes the assassins, and the murder is a genuine crime, and the verdict is right. But the reason those particular men were carrying that particular grudge is sitting there in a parenthesis, waiting seventeen chapters for anyone to notice.
Why this cluster is worth the depth
None of this made it into a Sunday. There wasn’t room, and there shouldn’t have been — a sermon has one job and this isn’t it.
But put the three together: a name that faithful, uncomfortable scribes rewrote for centuries because they couldn’t stand to leave it; a body disassembled piece by piece across a single chapter; and a betrayal that came not from outside the house but from a wound the house itself had inflicted two generations earlier. That’s a remarkable amount of literary and theological work happening almost entirely under the surface of a passage most people read as filler between the good parts.
It rewards exactly the kind of second, slower look a sermon never has time to give it.