Which versions of ynab_api are malicious?

The following npm versions of ynab_api are flagged malicious: 1.0.0, 99.0.0. Treat any of these as compromised.

How do I remediate ynab_api if I installed it?

Remove ynab_api from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ynab_api — how do I know if it already compromised me?

If ynab_api was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ynab_api part of a known attack campaign?

Yes — ynab_api is associated with the GHSA-vxxr-9qv6-7gr9, RLMA-2025-05567, RLUA-2025-06006 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ynab_api across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ynab_api (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ynab_api across your stack and pipelines.

Malicious package

ynab_apinpm

ynab_api is a confirmed malicious npm package (MAL-2025-48442) that executes malicious code on install (malicious versions 1.0.0, 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ynab_api (npm)

MAL-2025-48442

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ynab_api

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.099.0.0

Indicators of compromise (SHA-256)

89651853affef6883ac4048c42b47d47b023d454db86fecabcd3b8ec15f1c0f8

1301b631525e224768e7cfc45e52cdfa18d95b0e8cd5a7308b838037464c8946

7cd6b98f088a5af6ef065211b4f93294523b17a26273dbf1946d769cf0c45655

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ynab_api (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ynab_api across your stack and pipelines.
If you installed it — respond
Remove ynab_api from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ynab_api was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ynab_api before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ynab_api on npm has been identified as a malicious package (versions 1.0.0, 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vxxr-9qv6-7gr9RLMA-2025-05567RLUA-2025-06006

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ynab_api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database