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

realestate-asknpm

Malicious code in realestate-ask (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-944
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall realestate-ask

What this malware does

The package realestate-ask 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 'realestate-ask' @ 0.0.200 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
0.0.200

Indicators of compromise (SHA-256)

114f5b2c644f97feb01b885145ba9da1742c66b96e0b5e85c8717980528c74dd
bc4db310e1c17bbf02575dc3a75ab56d4d38581001d31617c583443f7d88a126
75a155e1870bd51f018f66476427d1da99c87cbbcab800c354dad13f76b67c3b

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 realestate-ask (version 0.0.200). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging realestate-ask across your stack and pipelines.

  2. If you installed it — respond

    Remove realestate-ask 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 realestate-ask 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 realestate-ask 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. realestate-ask on npm has been identified as a malicious package (version 0.0.200 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cq58-2656-w9f6

References

Credits

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

Detect & block this

O3 blocks realestate-ask-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.

realestate-ask (npm) malicious package — MAL-2026-944 | O3 Security