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

@realty-front/adnpm

@realty-front/ad is a confirmed malicious npm package (MAL-2024-1727) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.13.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @realty-front/ad (npm)

MAL-2024-1727
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @realty-front/ad

Malicious versions

4 flagged
1.0.01.0.11.13.11.13.2

Indicators of compromise (SHA-256)

fc976ce5dd352d3c7b0b310f5c9a3fb86d51182dd4d9f4b5d20db5e3dccdd812
117eec85c51e7da8a20a7c38cbe720c341e6a3fca02461e42a22fcdd48a6c118
f6ccf1708195a26322cc885042851ad85af55b07941453a324da4d2dd905c9ad

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

  2. If you installed it — respond

    Remove @realty-front/ad 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 @realty-front/ad 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 @realty-front/ad 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. @realty-front/ad on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.13.1, 1.13.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-00179RLUA-2024-06021

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @realty-front/ad-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

@realty-front/ad (npm) malicious package — MAL-2024-1727 | O3 Security