Which versions of airbnb-calendar are malicious?

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

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

airbnb-calendar 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.

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

If airbnb-calendar 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-calendar part of a known attack campaign?

Yes — airbnb-calendar is associated with the GHSA-rpm9-84m3-4j2j, RLMA-2025-05682 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-calendar 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-calendar (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-calendar across your stack and pipelines.

Malicious package

airbnb-calendarnpm

airbnb-calendar is a confirmed malicious npm package (MAL-2025-48979) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in airbnb-calendar (npm)

MAL-2025-48979

Immediate action

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

npm uninstall airbnb-calendar

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

8bdd7ff1ebc82ab66444ee41ee81408d4c29440e9a5662b9d11c4734d8a3a0c9

e80459e015e94c1ea76d050dbaee456b26ec604089695f1fc7f60dd55ca3cb28

8ea80dcfb7465190ad8311ee3b0164d1125f2f8456f297ddcc84c35665d032ad

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for airbnb-calendar (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-calendar across your stack and pipelines.
If you installed it — respond
airbnb-calendar 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.
Did it already run?
If airbnb-calendar 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-calendar 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-calendar 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

GHSA-rpm9-84m3-4j2jRLMA-2025-05682

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks airbnb-calendar-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database