Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

car-configurationnpm

car-configuration is a confirmed malicious npm package (MAL-2025-47054) that executes malicious code on install (malicious versions 2.0.10, 15.11.3, 15.11.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in car-configuration (npm)

MAL-2025-47054
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall car-configuration

What this malware does

The package communicates with a domain associated with malicious activity.

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

5 flagged
2.0.1015.11.315.11.415.11.515.11.6

Indicators of compromise (SHA-256)

bdbf9748a3a58d22a8e743b19e6a1b1d190d946e25490ccd6e313c16426b3782
089f29c9c2897c93afee98e57ed5b623bd605acdceb75a85eaaae087a862f6d0
ad032e78de953c6839d2a5eda8e7bc48470e256fd14aa739ecf269459fbf061d
ffabe32679d3ec56ca8f74fd010c7cb2b507754e40284ad3f022853417bdc74c

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove car-configuration 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.

  3. Did it already run?

    If car-configuration 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.

  4. How O3 protects you

    O3 blocks car-configuration 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. car-configuration on npm has been identified as a malicious package (versions 2.0.10, 15.11.3, 15.11.4, 15.11.5, 15.11.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hvqj-q8jv-4288RLMA-2025-04939RLUA-2026-01137

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks car-configuration-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.

Explore

car-configuration (npm) malicious package — MAL-2025-47054 | O3 Security