Which versions of a-onesite are malicious?

The following npm versions of a-onesite are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate a-onesite if I installed it?

a-onesite establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed a-onesite — how do I know if it already compromised me?

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

Yes — a-onesite is associated with the IN-MAL-2026-020495 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 a-onesite 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 a-onesite (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging a-onesite across your stack and pipelines.

Malicious package

a-onesitenpm

a-onesite is a confirmed malicious npm package (MAL-2026-16480) that opens a backdoor for remote access (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in a-onesite (npm)

MAL-2026-16480

Immediate action

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

npm uninstall a-onesite

What this malware does

[email protected] ships an empty index.js and no library functionality. Its package.json declares preinstall, preupdate, and test scripts that all invoke wget against http://eoy34oyrep9j5x8.m.pipedream.net with the installer's username ($(whoami)), current working directory ($(pwd)), and hostname ($(hostname)) as query parameters. The preinstall hook fires automatically on npm install, sending installer-identifying reconnaissance data over plaintext HTTP to a third-party collection endpoint unrelated to any advertised purpose. The version number (99.9.9) and empty code payload are consistent with a dependency-confusion reconnaissance beacon rather than a functional package.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

1b1ed6ca931448c083b5356eae6ad5af3cce9011d70fce4ce4ad427349991856

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for a-onesite (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging a-onesite across your stack and pipelines.
If you installed it — respond
a-onesite establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If a-onesite 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 a-onesite 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. a-onesite on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020495

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks a-onesite-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database