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

airbnb-vermeer-nodenpm

Malicious code in airbnb-vermeer-node (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190607
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall airbnb-vermeer-node

What this malware does

The package airbnb-vermeer-node was found to contain malicious code.

The OpenSSF Package Analysis project identified 'airbnb-vermeer-node' @ 95.6.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
95.6.0

Indicators of compromise (SHA-256)

5d0946afb04854d2b08aa05a71daab475236d7c62c29b4d419937b924476e1fa
d15f2b16fc6904b39ed8ae073822dc4a01bf2613ba243b3c2787740dd3cf2fc4

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

  2. If you installed it — respond

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

Credits

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

Detect & block this

O3 blocks airbnb-vermeer-node-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.

airbnb-vermeer-node (npm) malicious package — MAL-2025-190607 | O3 Security