Which versions of airbnb-internal are malicious?

The following npm versions of airbnb-internal are flagged malicious: 1.9.9, 999.9.9. Treat any of these as compromised.

How do I remediate airbnb-internal if I installed it?

Remove airbnb-internal 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.

I already installed airbnb-internal — how do I know if it already compromised me?

If airbnb-internal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is airbnb-internal part of a known attack campaign?

Yes — airbnb-internal is associated with the RLMA-2025-00612, RLUA-2026-01885 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find airbnb-internal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for airbnb-internal (2 malicious versions).

Malicious package

airbnb-internalnpm

Advisory published Mar 3, 2025Updated Apr 16, 2026

airbnb-internal is a confirmed malicious npm package (MAL-2025-1713) that executes malicious code on install (malicious versions 1.9.9, 999.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in airbnb-internal (npm)

MAL-2025-1713

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall airbnb-internal

Malicious versions

2 flagged

1.9.9999.9.9

Indicators of compromise (SHA-256)

6c278590cd5b49bf8291b378dc77475f96c2f06fdf3a452a7b82515c0f181c55

2f024f95dd497c17e391a9615738530f4a442bcd654c587229c3c102b05f25ec

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for airbnb-internal (2 malicious versions).
If you installed it — respond
Remove airbnb-internal 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.
Did it already run?
If airbnb-internal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. airbnb-internal on npm has been identified as a malicious package (versions 1.9.9, 999.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-00612RLUA-2026-01885

Credits

ReversingLabs · finder

Detect & block this

O3 blocks airbnb-internal-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