Which versions of atm_bmw are malicious?

The following npm versions of atm_bmw are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate atm_bmw if I installed it?

Remove atm_bmw 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 atm_bmw — how do I know if it already compromised me?

If atm_bmw 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 atm_bmw part of a known attack campaign?

Yes — atm_bmw is associated with the GHSA-r7mc-c86h-c2h3 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 atm_bmw 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 atm_bmw (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging atm_bmw across your stack and pipelines.

Malicious package

atm_bmwnpm

Malicious code in atm_bmw (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-34

Immediate action

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

npm uninstall atm_bmw

What this malware does

The package atm_bmw was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'atm_bmw' @ 2.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

65e1253a1ffde4534f1ba20d215fb248aa841e4ee082e9613365b5324d0a93bd

aca0601b1d8613895ac524d33f93ab92365d464e80eb526e58e2ca919abba129

20fd437233c7e774bdca9f661a997a94bd0d8373866763c3638f9bc12c588c5e

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 atm_bmw (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging atm_bmw across your stack and pipelines.
If you installed it — respond
Remove atm_bmw 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 atm_bmw 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 atm_bmw 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. atm_bmw on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r7mc-c86h-c2h3

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks atm_bmw-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