In 30 seconds
Security firm OX Security has reportedly found a stealer, malware whose whole job is to siphon credentials and other secrets, hiding inside a popular open source package that they say pulls about 192,000 downloads a month. The detail that makes this one stand out: the malicious code is said to run even when no project imports the package, so the install alone may be enough to trigger it. A digest account summarized the findings on X, pointing back to a writeup hosted on opensourcemalware.com.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listopensourcemalware.comopensourcemalware.com · rssOpen original sourceSee in source list
What happened
The public trail starts with a research writeup published on opensourcemalware.com, under a URL that references a compromised package called agent-framework on PyPI. The full text of that page was not captured in this batch, so its details reach us secondhand.opensourcemalware.comopensourcemalware.com · rssOpen original sourceSee in source list
On X, the IntCyberDigest account relayed the core findings and attributed them to OX Security: a stealer sits inside the package, and it executes even if nothing in the victim project imports it. The same post credits OX Security with the download estimate of roughly 192,000 per month.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Why it matters
Most supply chain warnings only bite code that actually calls the malicious library. If the no-import claim holds, the blast radius widens considerably: any machine or CI runner where the package lands during a dependency install could be exposed, whether or not the project's code ever uses it.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Stealers generally go after the crown jewels of a developer machine, things like API tokens, SSH keys and environment variables. A foothold inside a heavily downloaded package is therefore a short path to source code repositories and cloud accounts, which is why researchers flag install-time behavior so seriously.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What to do
The practical takeaway is straightforward dependency hygiene. Audit your manifests and lockfiles for anything you cannot vouch for, and treat any package matching the researchers' description as suspect until a name is confirmed. If you do find it in an environment, remove it and rotate the credentials that lived on the machines where it ran.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
It is also worth reviewing what executes at install time, not just what your code imports. That is the exact gap this report describes, and closing it mechanically, with pinned versions and restricted install scripts, shrinks the risk of the next package that tries the same trick.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Confirmed and still uncertain
Two claims anchor the public record so far, both attributed to OX Security through a secondary summary: the package draws about 192,000 downloads a month, and the payload runs without an import. Neither has been checked against a vendor advisory or the registry itself in the material available here.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Even the registry is fuzzy in this batch. The writeup URL on opensourcemalware.com references a PyPI package, while the circulating summaries never name the registry or the package itself, so readers should not assume which ecosystem is affected until the details land.opensourcemalware.comopensourcemalware.com · rssOpen original sourceSee in source listIntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What remains genuinely unknown: the package name, who is behind the campaign, how the code executes without being imported, and whether anyone's data was actually taken. Those answers will have to come from the full writeup or a registry takedown notice.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listopensourcemalware.comopensourcemalware.com · rssOpen original sourceSee in source list
What people are saying
The loudest voice so far is IntCyberDigest, which posted the summary on X and pushes the same feed through its Telegram channel and newsletter. Its framing is matter-of-fact, leading with the hook that the stealer runs without an import and quoting the download count.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listt.met.me · rssOpen original sourceSee in source listinternationalcyberdigest.cominternationalcyberdigest.com · rssOpen original sourceSee in source list
OX Security is the named source behind both the behavior claim and the 192,000 figure, as relayed by IntCyberDigest. The researchers' original publication did not appear in this batch, so their words reach us filtered through one intermediary.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Evolution
The story is still in its first act. It began as a writeup on opensourcemalware.com and was compressed almost immediately into a single shareable line by the digest account: the stealer runs without an import, and the package has 192,000 monthly downloads.opensourcemalware.comopensourcemalware.com · rssOpen original sourceSee in source listIntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
What has not evolved yet is specificity. The early summaries carry the alarming hooks but not the package name, the mechanism or the registry confirmation, so expect the next beat to be one of three things: a takedown, a vendor advisory, or the full technical writeup circulating more widely.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Reach
3 independent groups, 1 updates, and 1 engagements.
Technical detail
The one hard technical detail in the public summary is the import bypass. Importing is the explicit line of code that pulls a library into your running program, and most security reviews only look at what a project imports. This payload is said not to need that step at all.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
How it pulls that off is not explained in the available material. Code that runs without being imported typically rides on hooks that fire during installation, but that is an inference about this case, not something the captured sources document.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source list
Sources and evidence
The evidence base here is thin. It consists of an X post from IntCyberDigest carrying the findings, a writeup page on opensourcemalware.com whose body text was not captured, and the Telegram and newsletter channels that distribute the same digest. Everything substantive traces to one summary of one research report.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listopensourcemalware.comopensourcemalware.com · rssOpen original sourceSee in source listt.met.me · rssOpen original sourceSee in source list
Confidence should be calibrated accordingly. The behavior claim and the download figures are attributed to OX Security through a secondary account, not verified against the writeup text or registry data. Treat the specifics as reported until the primary research is directly accessible.IntCyberDigestx.com · IntCyberDigest · xOpen original sourceSee in source listopensourcemalware.comopensourcemalware.com · rssOpen original sourceSee in source list
Sources
- IntCyberDigestx.com · IntCyberDigest · x
- opensourcemalware.comopensourcemalware.com · rss
- t.met.me · rss
- internationalcyberdigest.cominternationalcyberdigest.com · rss



