What does the @taxify/city-borders malware do?

The OpenSSF Package Analysis project identified '@taxify/city-borders' @ 10.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of @taxify/city-borders are malicious?

The following npm versions of @taxify/city-borders are flagged malicious: 8.999.0, 10.0.0, 10.0.5. Treat any of these as compromised.

How do I remediate @taxify/city-borders if I installed it?

Remove @taxify/city-borders from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @taxify/city-borders — how do I know if it already compromised me?

If @taxify/city-borders 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 @taxify/city-borders part of a known attack campaign?

Yes — @taxify/city-borders is associated with the RLMA-2024-06047 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 @taxify/city-borders 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 @taxify/city-borders (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @taxify/city-borders across your stack and pipelines.

Part of a larger attack: @taxify published 10 malicious packages. See the full campaign →

Malicious package

@taxify/city-bordersnpm

@taxify/city-borders is a confirmed malicious npm package (MAL-2024-7901) that executes malicious code on install (malicious versions 8.999.0, 10.0.0, 10.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @taxify/city-borders (npm)

MAL-2024-7901

Immediate action

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

npm uninstall @taxify/city-borders

What this malware does

The OpenSSF Package Analysis project identified '@taxify/city-borders' @ 10.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

8.999.010.0.010.0.5

Indicators of compromise (SHA-256)

041f06eacb4e8e5ffe66ccd96009305833355630bf63940b876d7c7f3ce7bd55

b15c46bb7fe7b8c1da8e15f601cad511d07014aee56a51e5dc64cdf138e88fd0

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @taxify/city-borders (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @taxify/city-borders across your stack and pipelines.
If you installed it — respond
Remove @taxify/city-borders from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @taxify/city-borders 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 @taxify/city-borders 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. @taxify/city-borders on npm has been identified as a malicious package (versions 8.999.0, 10.0.0, 10.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-06047

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks @taxify/city-borders-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

Explore

All malware advisories How O3 detects malware Vulnerability database