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

@eagleview/ev-mapviewer-interactionsnpm

Malicious code in @eagleview/ev-mapviewer-interactions (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190621
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @eagleview/ev-mapviewer-interactions

What this malware does

Package is malware. It exfiltrates sensitive info, executes arbitrary code during install, and matches multiple YARA rules.

The package @eagleview/ev-mapviewer-interactions was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

e2d7da79dc7cea55b1c51c17952322ec30f3d03000a7b075252e9f74084a7a06

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @eagleview/ev-mapviewer-interactions (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @eagleview/ev-mapviewer-interactions across your stack and pipelines.

  2. If you installed it — respond

    @eagleview/ev-mapviewer-interactions is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @eagleview/ev-mapviewer-interactions 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 @eagleview/ev-mapviewer-interactions 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. @eagleview/ev-mapviewer-interactions on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks @eagleview/ev-mapviewer-interactions-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

@eagleview/ev-mapviewer-interactions (npm) malicious package — MAL-2025-190621 | O3 Security