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

@adac-fahrzeugplattform/uinpm

Malicious code in @adac-fahrzeugplattform/ui (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2282
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @adac-fahrzeugplattform/ui

What this malware does

The package @adac-fahrzeugplattform/ui 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 '@adac-fahrzeugplattform/ui' @ 99.9.9 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
99.9.999.9.11

Indicators of compromise (SHA-256)

9d32eaf9f87e33988e5e3677089359245c729d8a5ed621afbeac27d9f0644895
d66f65816d19b3566ffa3bd6fd250a54837a57fc57a036bd67452cfe9f14c512
779ce69d66db89d0bc1c8b82a373e6fed7e1b6a84d2cdf56bcab4b3076226f5f
65c7603efc4b3bb8b75912c9bfff75d30c0ce6b040c6d7fd5ad7af1c6ab45ff4

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 @adac-fahrzeugplattform/ui (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @adac-fahrzeugplattform/ui across your stack and pipelines.

  2. If you installed it — respond

    Remove @adac-fahrzeugplattform/ui 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 @adac-fahrzeugplattform/ui 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 @adac-fahrzeugplattform/ui 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. @adac-fahrzeugplattform/ui on npm has been identified as a malicious package (versions 99.9.9, 99.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-96gm-xh35-6xfw

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @adac-fahrzeugplattform/ui-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.

@adac-fahrzeugplattform/ui (npm) malicious package — MAL-2026-2282 | O3 Security