Which versions of mapkit-example-vanillajs are malicious?

The following npm versions of mapkit-example-vanillajs are flagged malicious: 1.3.0. Treat any of these as compromised.

How do I remediate mapkit-example-vanillajs if I installed it?

Remove mapkit-example-vanillajs 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 mapkit-example-vanillajs — how do I know if it already compromised me?

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

Yes — mapkit-example-vanillajs is associated with the GHSA-w856-vp94-4mqj 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 mapkit-example-vanillajs 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 mapkit-example-vanillajs (version 1.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mapkit-example-vanillajs across your stack and pipelines.

Malicious package

mapkit-example-vanillajsnpm

Malicious code in mapkit-example-vanillajs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-327

Immediate action

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

npm uninstall mapkit-example-vanillajs

What this malware does

The package mapkit-example-vanillajs was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'mapkit-example-vanillajs' @ 1.3.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.3.0

Indicators of compromise (SHA-256)

03576999871a27b531ba136d78dbaeaec56a63cfd7abc1616d5437dea4a5286d

e4444c4384bc61fe285647ae3fa5fa1ae0e79116dceff54c86b9cc589fd31ffe

5930ccf1bb06110abd9daaa0441059f428ee853e926572c4c9416ba959401d53

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 mapkit-example-vanillajs (version 1.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mapkit-example-vanillajs across your stack and pipelines.
If you installed it — respond
Remove mapkit-example-vanillajs 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 mapkit-example-vanillajs 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 mapkit-example-vanillajs 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. mapkit-example-vanillajs on npm has been identified as a malicious package (version 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w856-vp94-4mqj

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks mapkit-example-vanillajs-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