FANDOM


Stub templates just show off a wiki's flaws. Instead of using a stub template, make the page better!

This article is incomplete. Please add information to make it more complete and to fit the standards of this wiki.

Cyberchase
Season 1, Episode 16
Air date February 11, 2002
Written by Dave Dias (Story)
George Arthur Bloom
Directed by Larry Jacobs
Episode Guide
previous
"Find Those Gleamers!"
next
"Return to Sensible Flats"

"Codename: Icky" is the 16th episode of the first season of Cyberchase. It originally aired on February 11, 2002.

Characters

Main Characters

Recurring/Minor Characters

Places

Plot

In the watery depths of cybersite Aquari-yum, the kids and Hacker go in search of a giant cyber-slug, who feeds on pure energy. The kids and Digit travel underwater in two separate vessels, but Hacker has a listening device that taps into their communications system, allowing him to overhear their plans and track every move they make. The kids outsmart Hacker by devising a series of codes so they can send messages back and forth in secret — even though Hacker can hear what they’re saying. But unless the kids can reach the slug first, Hacker will use the slug to attack Motherboard’s circuitry and disable her once and for all!

Extras

  • Math topic: "Codename: Icky" focuses on codes with rules.
  • For Real Segment: "Harry's Cracked Code": Harry and his friend, Julio, have found an ancient Viking alphabet (actually very similar to Cirth in Lord of the Rings) to send coded messages to each other. For fun, Julio uses the code to invite Harry to a special event. Harry decodes part of Julio's invitation, then stops when he thinks he knows the rest. So, why is he the only one who shows up at Julio's in costume Saturday night?

Transcript

External Links

PBS KIDS - Cyberchase Videos - Codename: Icky

Gallery

External links

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.