Unless someone familiar with that app can tell you where and how it gets its ads, you could first try to click on the ad and see which domain it points to. If it's an ad server, you can easily blacklist it, but apps often rely on third party ad providers much harder to spot, or even embed ads in their own domain. The best way would be to use a packet sniffer to monitor your apps' traffic but that's beyond the scope of this thread. Before you spend too much time on this, verify that you have tried with the default packages enabled since they already cover a lot of known ad mongers. Keep in mind that not all ads can be blocked by the Knox firewall, an issue over which SABS has no control.
From a practical standpoint, I suspect you may be using the "FREE" version of your app and that simply purchasing the ad-free version would solve the problem nicely!
---------- Post added at 08:59 AM ---------- Previous post was at 08:49 AM ----------
I think that package names that include "sabs" (or "adhell") could be black listed by some big phone manufacturer who doesn't want you to use knox to disable preinstalled apks, block ads and change some permissions, so license validation may fail if package name is not changed?
Not quite. Samsung publishes a full Knox API but they only allows a very limited number (10?) of "test" active apps bearing the same package name unless provided by a recognized full Samsung Developer (a rather expensive endeavor), and it's not even clear whether they'd allow outsiders to publish such apps. They're not necessarily evil, they are mainly protecting themselves and their partners. Changing the package name is a convenient way to get around those limitations at least for now.