> Note: Initially submitted this to MSRC (VULN-172488), MSRC insisted bypassing billing is outside of MSRC scope and instructed me multiple times to file as a public bug report.
Good job, Microsoft.
bazodedotoday at 9:14 PM
The "premium request" billing model where you pay per invocation and not for usage is very obviously not a sustainable approach and creates skewed incentives (e.g. for microsoft to degrade response quality), especially with the shift towards longer running agentic sessions as opposed to simple oneshot chat questions, which the system was presumably designed for. Its just a very obvious fundamental incompatibility and the system is in increasing need of replacement. Usage linked (pay per token) is probably the way to go, as is industry standard.
> The right script, with the right prompts can be tailored to create a loop, allowing the premium model to continually be invoked unlimited times for no additional cost beyond that of the initial message.
Ralph loops for free...
sciencejerktoday at 6:00 PM
Have confirmed that many of these AI agents and Agentic IDEs implement business logic and guardrails LOCALLY on the device.
(Source: submitted similar issue to different Agentic LLM provider)
ramon156today at 5:10 PM
The laat comment is a person pretending to be a maintainer of Microsoft. I have a gut feeling that these kind of people will only increase, and we'll have vibe engineers scouring popular repositories to ""contribute"" (note that the suggested fix is vague).
I completely understand why some projects are in whitelist-contributors-only mode. It's becoming a mess.
everfrustratedtoday at 8:50 PM
Copilot fairly recently added support for running sub-agents using different models to the model that invoked them.
If this report is to be believed, they didn't implement billing correctly for the sub-agents allowing more costly models to be run for free as sub-agents.
peacebeardtoday at 5:14 PM
My guess is either someone raised this internally and was told it was fine, or knew but didn't bother raising it since they knew they’d be blown off.
light_hue_1today at 5:20 PM
Why would you report this?!
A second time. When they already closed your first issue. Just enjoy the free ride.
direwolf20today at 6:51 PM
Who would report this? Are they hoping for a bug bounty or they know their competitors are using the technique?
zkmontoday at 5:14 PM
Nothing compared to pirated CDs with Office and Windows, 20 yrs back.
blibbletoday at 5:13 PM
the "AI" bot closing the issue here is particularly funny
AustinDevtoday at 5:03 PM
Is it just me or is Microsoft really phoning it in recently?
jlaroccotoday at 7:23 PM
I'm sure they'll fix this, but it would be funny if the downfall of AI was the ability to use it to hack around its own billing.
thenewwazootoday at 5:40 PM
Every time I see something about trying to control an LLM by sending instructions to the LLM, I wonder: have we really learned nothing of the pitfalls of in-band signaling since the days of phreaking?
VerifiedReportstoday at 5:10 PM
Billing for what?
pixelmelttoday at 5:06 PM
Was good while it lasted, I hope Microsoft continues their new tradition of vibe coding their billing systems :p