Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @ozon-shared-deps published 9 malicious packages. See the full campaign →
Malicious package

@ozon-shared-deps/ozon-maps__map-sdknpm

@ozon-shared-deps/ozon-maps__map-sdk is a confirmed malicious npm package (MAL-2024-2820) that executes malicious code on install (malicious versions 2.6.6, 2.6.20). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ozon-shared-deps/ozon-maps__map-sdk (npm)

MAL-2024-2820
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ozon-shared-deps/ozon-maps__map-sdk

Malicious versions

2 flagged
2.6.62.6.20

Indicators of compromise (SHA-256)

ce8c0a41f0192d38a50f2510068810356b21a95c9242b7fec2cfb103963e26f2
6c30b13423d0babcad428fcce7296ce7af39243007765b64ec313284928c004e
7981a527d89e4245b12fe6a8e36f37503ac4ba9c800433699a1c75f7d3c1a02c

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

  2. If you installed it — respond

    Remove @ozon-shared-deps/ozon-maps__map-sdk 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 @ozon-shared-deps/ozon-maps__map-sdk 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 @ozon-shared-deps/ozon-maps__map-sdk 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. @ozon-shared-deps/ozon-maps__map-sdk on npm has been identified as a malicious package (versions 2.6.6, 2.6.20 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00163RLUA-2024-06003

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @ozon-shared-deps/ozon-maps__map-sdk-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
@ozon-shared-deps/ozon-maps__map-sdk (npm) malicious package — MAL-2024-2820 | O3 Security