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

zalando-consent-apinpm

Malicious code in zalando-consent-api (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-729
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall zalando-consent-api

What this malware does

The package zalando-consent-api 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.

Malicious versions

2 flagged
0.0.1-security56.2.1

Indicators of compromise (SHA-256)

eca8a371c4dcf56c3c2406b08dca41d055cf185068780c798da328692d4ad2b2
cfebb7ed5c3e35afeff037425cd019134eb927484b619019f7d11b13d6fe59c5
00f1089ec179227bd5a2661de5605eeffb491828df4249393828bb339b7640cb

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 zalando-consent-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 zalando-consent-api across your stack and pipelines.

  2. If you installed it — respond

    Remove zalando-consent-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.

  3. Did it already run?

    If zalando-consent-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.

  4. How O3 protects you

    O3 blocks zalando-consent-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. zalando-consent-api on npm has been identified as a malicious package (versions 0.0.1-security, 56.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r6c3-cmw7-p4qrRLMA-2026-01669

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks zalando-consent-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.

zalando-consent-api (npm) malicious package — MAL-2026-729 | O3 Security